Naumu MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Naumu local stdio knowledge-graph access for clients without browser OAuth: Does the API-key fallback remain supported without conflating it with the separate remote OAuth connection?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Team knowledge-graph, notes and threaded collaboration for agents.

What we know

Remote OAuth or local API-key MCP over Naumu's hosted knowledge graph, with read/write access to schema, nodes, edges, notes, topics, attachments, threads and delegated tasks.

Maintenance / activity evidence

@naumu/mcp 0.18.3 published 2026-10-02T11:22:09.216Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Identity-scoped graph/collaboration read/write authority. Writes: Create/update/delete graph nodes/edges/schema; Create/update notes/topics/attachments; Post messages/reactions; Create delegated tasks.
OAuth or API key.
Sensitive access: Organizational knowledge, Private notes, Attachments, Member/collaboration content

Broad collaborative knowledge write surface; use least-privilege identities.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Does the API-key fallback remain supported without conflating it with the separate remote OAuth connection?

The bounded review of the publisher's documented Naumu local stdio knowledge-graph access for clients without browser OAuth and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Broad collaborative knowledge write surface; use least-privilege identities.
Identity-scoped graph/collaboration read/write authority.
OAuth or API key.
Knowledge graph, notes, messages and attachments are processed by Naumu; exact retention is unresolved.
Reviewed write actions: Create/update/delete graph nodes/edges/schema; Create/update notes/topics/attachments; Post messages/reactions; Create delegated tasks
Sensitive access: Organizational knowledge, Private notes, Attachments, Member/collaboration content
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
privacy/retention
pricing
Remote OAuth needs browser support; local mode needs API key.
Graph/schema writes can be destructive.
Privacy/retention and pricing were not established.

Original activity observations

@naumu/mcp 0.18.3 published 2026-10-02T11:22:09.216Z

Technical identity

npm/@naumu/mcp

Exact implementation source: https://www.npmjs.com/package/@naumu/mcp ↗
Reviewed resource type: MCP Server
Repository identity: naumu-ai/mcp
Package identity: npm:@naumu/mcp
Service endpoint: https://naumu.ai/api/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
@naumu/mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
Evidence source ↗
naumu.ai/docs/local-mcp
Source material retained for this review.
Includes references whose attribution is not established.
GitHub repository ↗
naumu-ai/mcp
Repository reference; implementation attribution is not established for every document.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Remote OAuth recommended. Local stdio route needs NAUMU_API_KEY.
publisher install or stdio launch · Claude Code only · Publisher instructions
claude mcp add --transport http --scope user naumu https://naumu.ai/api/mcp
Configure / authenticate
MCP100 setup guide
Recommended remote OAuth connector https://naumu.ai/api/mcp; local package is fallback for older stdio-only clients and uses API key.
Check connection
Suggested check
For preferred remote OAuth https://naumu.ai/api/mcp, sign in and perform read-only knowledge retrieval. For local stdio, configure API key separately.
Remove / uninstall / revoke
MCP100 setup guide
If you added this integration to Claude Code under the registration name `naumu`, run `claude mcp remove naumu` to unregister that client entry. In Claude Desktop, Cursor, VS Code or another host, delete/disable the corresponding named MCP registration in that host's settings and restart/reconnect. If you installed an npm package globally or operate a separate HTTP server, uninstall/stop it with its original deployment method. This does not delete user data or revoke service credentials.
MCP client unregister, stopping hosted processes, package uninstall, OAuth disconnect and token revocation are distinct actions.
A claude mcp remove command is only valid for Claude Code when the local registration actually has that name. Other MCP hosts require their own UI/config cleanup.
Separate credential guidance / limitations: Official Naumu Settings -> Your agents -> Active access supports revocation of connected agent grants.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove naumu

Official Documentation & Sources

What it does

Remote OAuth or local API-key MCP over Naumu's hosted knowledge graph, with read/write access to schema, nodes, edges, notes, topics, attachments, threads and delegated tasks.

Capability: Files & Knowledge
Resource type: MCP Server
Best fit: Team knowledge-graph, notes and threaded collaboration for agents.

Representative uses

Read/search team graph and notes
Create/update/delete nodes and edges
Manage topics/notes/attachments
Post messages/reactions and delegate tasks

Limitations

Remote OAuth needs browser support; local mode needs API key.
Graph/schema writes can be destructive.
Privacy/retention and pricing were not established.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: OAuth or API key.
Permissions: Identity-scoped graph/collaboration read/write authority.
Data handling: Knowledge graph, notes, messages and attachments are processed by Naumu; exact retention is unresolved.
Cost: unknown
Risk and cautions: Broad collaborative knowledge write surface; use least-privilege identities.

Access scope and cautions

Write actions: Create/update/delete graph nodes/edges/schema Create/update notes/topics/attachments Post messages/reactions Create delegated tasks
Sensitive access: Organizational knowledge Private notes Attachments Member/collaboration content
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Read/search team graph and notes; Create/update/delete nodes and edges; Manage topics/notes/attachments; Post messages/reactions and delegate tasks.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @naumu/mcp. Recorded endpoint: https://naumu.ai/api/mcp. Recorded transport: stdio, streamable_http. Recorded environment-variable notes: NAUMU_API_KEY (local). No configuration values are supplied here. Prerequisites: Naumu account; MCP client. Client notes: Use separate bot/tool keys and revoke unused OAuth grants/keys. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Hosted OAuth 2.1 or local `nmu_` API key.

Can it modify data or perform write operations?

Documented write actions include: Create/update/delete graph nodes/edges/schema; Create/update notes/topics/attachments; Post messages/reactions; Create delegated tasks. Recorded permission boundary: Identity-scoped graph/collaboration read/write authority.

What data-handling boundary should I consider?

Knowledge graph, notes, messages and attachments are processed by Naumu; exact retention is unresolved. Recorded sensitive-access context: Organizational knowledge; Private notes; Attachments; Member/collaboration content.

What limitations and risks should I check before use?

Broad collaborative knowledge write surface; use least-privilege identities. Remote OAuth needs browser support; local mode needs API key. Graph/schema writes can be destructive. Privacy/retention and pricing were not established. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

Is this an official MCP?

Naumu is listed as First-party MCP in MCP100’s current evidence.