Local MCP
Connect local AI coding agents like Claude Code and Cursor to Naumu with an API key.
AI coding agents that run on your machine — like Claude Code and Cursor — connect to Naumu through a local MCP server you run yourself, authenticated with an API key rather than a browser sign-in.
The server is published as the @naumu/mcp package on npm. You don't install it globally; your agent launches it on demand with npx.
Get an API key
- Open Settings → API Keys.
- Select Create API Key and give it a recognizable name (such as the tool it's for).
- Copy the key right away — it's shown only once and cannot be retrieved later. Keys start with
nmu_.
The key lets the local server act in Naumu as you, with your exact permissions. You can revoke it at any time from the same screen; see Account settings for more.
Claude Code
Register the server once, scoped to your user, passing the key as an environment variable:
claude mcp add naumu -s user \
-e NAUMU_API_KEY=nmu_your_key_here \
-- npx -y -p @naumu/mcp naumu-mcpNaumu's tools are then available in every Claude Code session.
Cursor
Add the server to your Cursor MCP settings:
{
"mcpServers": {
"naumu": {
"command": "npx",
"args": ["-y", "-p", "@naumu/mcp", "naumu-mcp"],
"env": {
"NAUMU_API_KEY": "nmu_your_key_here"
}
}
}
}Other MCP-capable agents follow the same shape: run npx -y -p @naumu/mcp naumu-mcp with NAUMU_API_KEY set in the environment.
Environment variables
| Variable | Required | Default | Description |
|---|---|---|---|
NAUMU_API_KEY | Yes | — | Your API key (starts with nmu_) |
NAUMU_API_URL | No | https://naumu.ai | Naumu API base URL (only change for self-hosted) |
Use a separate API key for each tool. That way, if one leaks, you can revoke just that key without disrupting the others.
Related
- Account settings — create and revoke the API keys local agents use.
- Claude — connect claude.ai over a remote MCP connector instead.
- Search — how the search tools rank results across your spaces.