Naumu

What Naumu MCP server does

The Naumu MCP server gives an MCP client access to Naumu spaces, which are knowledge graphs containing typed nodes, attributes, connections, notes, and discussion threads. Agents can discover accessible spaces, inspect members and schemas, search graph content, retrieve individual nodes, and ask questions that return synthesized answers with sources and confidence.

The server also exposes write operations. Agents can create or update nodes, add or remove edges, reparent nodes, modify schemas, and audit schema violations. Thread tools support listing conversations, reading messages, posting markdown, and delegating work to @Naumu for asynchronous processing. The README also documents note editing, topics, attachments, space admission, reactions, and ChatGPT-compatible search and fetch tools.

Reach for the Naumu MCP server when an agent needs shared organizational context rather than isolated files or a one-off document search. It is suitable for querying team knowledge, maintaining structured graph data, and coordinating work through Naumu threads.

How it works

Naumu provides two transports with the same main tool surface. The remote endpoint is https://naumu.ai/api/mcp and uses OAuth: the client opens a browser for sign-in and approval, and access can later be revoked from Naumu's agent settings. The local package communicates over stdio and is launched on demand by the client with npx.

Local authentication uses an API key. User keys identify the calling user, while bot identity keys can receive a restricted tool set based on their permissions. Bot-only operations include starting a new thread with participants and an initial message. Tool results can expose graph structure, node context, thread status, participant information, and sources for grounded answers.

Setup and configuration

For clients that support remote MCP with OAuth, register the server at https://naumu.ai/api/mcp. Claude Code can add it with an HTTP transport command, while Cursor uses an MCP server entry containing the URL. OAuth client credentials should be left blank for Cursor because Naumu handles registration during sign-in.

For local stdio use, create an API key under Naumu Settings > Your agents. The key is shown only once and starts with nmu_; using a separate key for each tool is recommended in the documentation. Clients launch the package with npx -y -p @naumu/mcp naumu-mcp and pass the key through NAUMU_API_KEY.

NAUMU_API_URL is optional and defaults to https://naumu.ai. It can be used when the client must target a different Naumu API base URL. The package is not installed globally; the MCP client runs it on demand.

Tools and capabilities

The Naumu MCP server groups its tools around several operations:

• Discover spaces, members, caller identity, schemas, topics, and admission status.
• Search by meaning and text, filter by node type and attributes, inspect connections, and identify dense hub nodes.
• Create, update, delete, and reparent nodes; add or remove individual or bulk edges.
• Replace or extend schemas with node types, attributes, and connections, then report violations.
• Ask @Naumu for node-grounded answers or delegate tasks that return a thread ID for polling.
• Read, create, and update threads, notes, attachments, and topic assignments where the identity has permission.

Several mutations are destructive. Removing a node also removes its connections, and note replacement or section deletion overwrites content. Bulk edge removal is atomic, while node and edge creation support bounded batches.

Limitations and notes

Remote OAuth is the recommended route when the client supports it, but the local package is intended for CI, bots, external-agent identities, and older stdio-only harnesses. Access depends on the authenticated key and space permissions; bot keys may expose fewer tools than user keys. The client must support the selected transport, and local use requires securely providing the API key.

The package repository is the public home for the published npm package, documentation, issues, and releases; development occurs in Naumu's monorepo. The available tool set includes client-specific compatibility wrappers named search and fetch for clients that require those literal names.