Contextium MCP Server vs Naumu — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Contextium MCP Server vs Naumu
In-depth architectural comparison of the Contextium MCP Server and Naumu MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Contextium MCP Server
Knowledge & Memory · Local stdio
Quality: 61/100 (Good) | Auth: API Key required
Naumu
Knowledge & Memory · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Verdict Summary: Choose Contextium MCP Server if you need specialized Knowledge & Memory tools running via a local process. Choose Naumu if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Contextium MCP Server when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
One shared context for every AI tool your team uses. Serves your team's knowledge, coding standards, skills, and AI agents to Claude, Cursor, Copilot, and any MCP client — load a whole workflow (docs, agents, skills, tasks, phases) in a single call. Versioned and permissioned. npx @contextium/mcp-server
Search, extend, and act on your team's Naumu knowledge graph: notes, threads, and nodes.
List all resources of a given type in a workspace — the fast way to see what already exists before you act. Returns lightweight summaries (IDs, names, key fields), not full content: use `get` for one resource's full detail, or `search` to find resources by text or tag. Set `type` to choose what to list — workspaces, libraries (context libraries), agents, skills, files (pass libraryId), workflows, tags, file_tags (pass fileId), workspace_status, or members (with roles + activity). Uses your active workspace when workspaceId is omitted.
get
Get full details of a resource by ID. Use workspace_activity for recent activity logs. Use activity_archive to read a specific month's archived logs by YYYY-MM (e.g. 2025-02). Use list_activity_archives to see which months have archives. Use workflow_activity for the activity digest since a workflow's last session. Use entity_activity for recent activity on a specific file or entity.
create
Create a new resource in a workspace. Set `type` to what you're creating: "file" (needs libraryId + title + complete content), "library" (a context library — needs name), or "agent" / "skill" / "workflow" (need name; a workflow can bundle projectIds, agentIds, skillIds, and tagIds). Always provide full, real content for files — never empty or placeholder.
File linking: to link to another file in the SAME workspace, put //<fileId> inline in the content — use the target file's UUID (from search/list/get results), not its title. The link renders as the target's title and is indexed automatically on save; the target gains a backlink with no extra step. Add a link only where the text genuinely references an existing file; never invent //<id> for a file that does not exist (it becomes a dangling link). Use get({ type: "file_links", id }) to inspect a file's links and backlinks.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Contextium MCP Server is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Naumu belongs to Knowledge & Memory using local stdio subprocess. Select Contextium MCP Server when you need capabilities focused on knowledge & memory and Naumu when you require tools for knowledge & memory.
Update an existing resource in place by ID — edit a file's title, path, content, or status, or rename/reconfigure an agent, skill, workflow, or project. Only the fields you pass are changed; for files, a new version is created automatically so history is preserved. Set `type` to the resource kind and `id` to its UUID (from list/search/get).
File linking (type=file): to link to another file in the SAME workspace, put //<fileId> inline in the content — use the target's UUID (from search/list/get results), not its title. The link renders as the target's title and is re-indexed on save; backlinks are automatic. To add a backlink to file B, add //<B-id> to this file's content. Remove a link by deleting its //<id> token. Only link to files that exist. Use get({ type: "file_links", id }) to inspect links and backlinks.
delete
Delete a resource (moves to trash, restorable). type: file | skill | workflow
search
Find files in a workspace when you don't know their exact ID. Pick a `mode`: "text" runs a full-text search over file contents and titles; "tags" returns files carrying ALL of the given tagIds (AND logic); "files" matches by partial file name/title. Reach for search before `get` when you only know roughly what you want; use `list` with type=files instead when you just need everything in a library. Optionally narrow to one library with libraryId.
suggest_libraries
Suggest existing context libraries that look relevant to a workflow you are about to create, ranked by keyword overlap between the workflow name/description and each library's name/description. Call this BEFORE create_workflow (or create type=workflow) so you can present the matches to the user and let them choose which to attach via projectIds. Nothing is auto-attached — these are suggestions only. Returns [] when no libraries score above zero.
load_workflow
Load complete workflow context — agents, skills, files, and libraries. Use this to initialise a full workflow session.
manage_relationship
Manage relationships: add/remove skills on agents, add/remove inline tags on files, and share/unshare a private workflow with an individual workspace member. For type=tag this EDITS THE FILE CONTENT — it writes (or deletes) a #<value> token in the file body, which is the source of truth for a file's tags; the tag is auto-created if new. (Equivalent to updating the file content yourself.) For type=workflow_member, add is an upsert (re-adding an existing member updates their role).
marketplace
Browse, inspect, and install shared skills, agents, and MCP servers from the Contextium Marketplace. Set `action`: "search" to browse listings (optionally filter by itemType skill/agent/mcp_server, category, or query); "get" for a listing's full details by slug; "install" to add a listing to a workspace by slug. Typically search first to find a slug, then get or install with it.
project
DEPRECATED — phases are now DB-backed. Use list_phases (replaces get_next_phase), update_phase_status(phaseId, "done") (replaces mark_phase_complete), and load_workflow (replaces load_session/close_session).
figma_sync
Manage Figma connector integrations — list connected files or trigger a sync to pull design tokens, components, and page structure into your Contextium libraries.
+57 more tools listed on main page
Naumu Tools (52)
naumu_list_graphs
List every space (graph) the key can access, with ids, names, and roles
naumu_create_graph
Create a new, empty space owned by the authenticated user
naumu_list_members
List a space's members with their roles
naumu_whoami
Return who the calling key is (user, or bot identity with its graph and allowed tools)
naumu_get_schema
Get a space's schema (node types, attributes, connections)
naumu_update_schema
Replace the schema with a full new definition
naumu_add_node_type
Add one node type without resending the whole schema
naumu_add_connection
Add one connection from an existing node type to another
naumu_add_attribute
Add or extend an attribute on an existing node type
naumu_list_schema_violations
Audit a space against its schema and report violations
naumu_search
Hybrid (meaning plus text) search over graph nodes
naumu_filter
Filter nodes by type and attributes, with deterministic and complete results