Naumu vs Memograph — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Naumu vs Memograph
In-depth architectural comparison of the Naumu and Memograph 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
Naumu
Knowledge & Memory · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Memograph
Knowledge & Memory · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Verdict Summary: Choose Naumu if you need specialized Knowledge & Memory tools running via a local process. Choose Memograph 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 Naumu when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: NAUMU_API_KEY, NAUMU_API_URL.
Naumu is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Memograph belongs to Knowledge & Memory using local stdio subprocess. Select Naumu when you need capabilities focused on knowledge & memory and Memograph when you require tools for knowledge & memory.
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
+40 more tools listed on main page
Memograph Tools (39)
search_vault
Search memories in the MemoGraph vault using semantic or keyword search
create_memory
Create a new memory in the MemoGraph vault
query_with_context
Retrieve relevant context from the vault for a question. If LLM provider is configured, can optionally generate an answer. Otherwise, returns context for the client's LLM to use.
get_vault_info
Get information about the currently configured MemoGraph vault (path, name, configuration). Use this when you need to know which vault is being used.
get_vault_stats
Get statistics about the currently configured MemoGraph vault (memory counts, types, tags)
list_memories
List memories with optional filters
get_memory
Get full content of a specific memory by ID
import_document
Import a document (TXT, PDF, DOCX) into the vault
delete_memory
Delete a memory from the vault by ID
update_memory
Update an existing memory's title, content, tags, or salience
batch_update
Update multiple memories in one efficient operation. Much faster than calling update_memory multiple times.
batch_delete
Delete multiple memories in one efficient operation. Much faster than calling delete_memory multiple times.