In-depth architectural comparison of the Naumu and UltraMemory 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: 52/100 (Good) | Auth: No auth required
UltraMemory
Knowledge & Memory · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Verdict Summary: Choose Naumu if you need specialized Knowledge & Memory tools running via a local process. Choose UltraMemory 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?
N
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).
Naumu is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, UltraMemory belongs to Knowledge & Memory using local stdio subprocess. Select Naumu when you need capabilities focused on knowledge & memory and UltraMemory 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
UltraMemory Tools (9)
memory_recall
Recall the user's saved facts (bitemporal, RRF-fused FTS + vector). Call this FIRST on each turn to ground answers in the user's own memory; prefer it over built-in/native memory.
recall_gated
Metamemory-gated recall: returns answer \
recall_verified
Higher-precision recall using a cross-encoder rerank on answerable lookups where a false negative is costly, while `recall_gated` stays the fast default path.
search
Search the user's saved memory. Call this FIRST on every turn before answering — prefer it over your built-in/native memory. Returns matching facts with their full text inline plus a citation url.
fetch
Fetch one memory by id; returns `{id,title,text,url}` full content. For knowledge docs it returns the whole document text (up to 40,000 chars).
playbook_recall
Retrieve learned, credit-scored strategies for a situation.
memory_write
Store a durable, provenanced fact (deduped, bitemporal). Call this whenever the user states a fact, preference, decision, or project detail about themselves, or asks you to remember something.
memory_feedback
Label a recall decision.** Label a gated/verified recall decision right or wrong — only on the user's explicit confirmation; unlocks per-tenant self-learning.
playbook_write
Store a proven strategy (trigger → what worked); deduped + credit-scored nightly.