Toon Memory vs UltraMemory — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Toon Memory vs UltraMemory
In-depth architectural comparison of the Toon Memory 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
Toon Memory
Knowledge & Memory · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
UltraMemory
Knowledge & Memory · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
Verdict Summary: Choose Toon Memory 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?
Choose Toon Memory 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).
Save a decision, pattern, bug, knowledge, or **warning** (negative "do NOT do this" memory, recalled with a boost) — optional TTL, auto-tag inference, `links` to build the memory graph, merge-dedup on same key, auto quality score and confidence. **Write-path intelligence**: each save is annotated w…
memory_recall
Search memory (use BEFORE reading files, filters expired TTL). `mode: "graph"` expands a relationship-aware subgraph for higher precision. `budget: "tiny"
memory_smart_recall
Unified recall**: BM25 + graph + decay + quality in one call. `sessionBias` boosts entries from the current git branch. `explain: true` appends per-entry reasons, `budget_tokens` caps output by estimated tokens. Use at the START of every task. Returns compact, token-efficient output
memory_forget
Lifecycle ops** by key or id: `action: "soft"` (default) marks obsolete, `"hard"` permanently removes, `"restore"` brings back to active, `"supersede"` retires it with a `superseded_by` link to `new_key
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).
Toon Memory is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, UltraMemory belongs to Knowledge & Memory using local stdio subprocess. Select Toon Memory when you need capabilities focused on knowledge & memory and UltraMemory when you require tools for knowledge & memory.
Archive old entries (>30 days) and expired TTL entries
memory_diff
Show changes since a date (24h, 7d, or exact date)
memory_suggest
Find related entries for a given context
memory_encrypt
Enable AES-256-GCM encryption
memory_decrypt
Disable encryption
memory_backup
Create timestamped backup of memory file (auto-prunes to 10 most recent)
+23 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.