Anneal Memory vs Basic Memory — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Anneal Memory vs Basic Memory
In-depth architectural comparison of the Anneal Memory and Basic Memory 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
Anneal Memory
Knowledge & Memory · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Basic Memory
Knowledge & Memory · Local stdio
Quality: 69/100 (Great) | Auth: No auth required
Verdict Summary: Choose Anneal Memory if you need specialized Knowledge & Memory tools running via a local process. Choose Basic Memory 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?
A
Choose Anneal 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).
Two-layer memory for AI agents with an immune system. Zero dependencies.
Persistent, local-first AI memory: a semantic knowledge graph of plain Markdown files that humans and LLMs both read and write. Works with any MCP client, with optional cloud sync and team workspaces.
When something important happens — a decision, observation, tension, question, outcome, or context change
recall
Before making decisions that might have prior context. Query by time, type, keyword, or ID
prepare_wrap
At session end — returns episodes + current continuity + association context + compression instructions
save_continuity
After compressing — server validates structure, citations, records associations, applies decay, and saves
delete_episode
Remove content that should not exist (PII, sensitive data). Cascades to associations. Logged in audit trail (best-effort: the deletion is never failed by an audit-write failure; check `status().audit_write_failures` when the log is your evidence — a loss *recorded* there survives the process, so a…
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).
Anneal Memory is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Basic Memory belongs to Knowledge & Memory using local stdio subprocess. Select Anneal Memory when you need capabilities focused on knowledge & memory and Basic Memory when you require tools for knowledge & memory.
Abandon a wrap that is open and will not be finished — the escape hatch when `prepare_wrap` refuses with "a wrap is already in progress". Episodes are not deleted; the next `prepare_wrap` picks them up. Optional `wrap_token`: cancel only if that wrap is still the one in progress, refused with no ch…
crystal_recall
Recall crystallized (graduated, long-term) patterns relevant to a query — the on-demand semantic tier. Keyword scoring is corpus-aware (rare, distinctive terms outweigh common process-words, so recall stays precise on a large store), and recall also follows evidence edges — surfacing a pattern grou…
crystal_index
The always-on name + one-clause menu of the crystallized store — what graduated wisdom exists, so the agent isn't blind to its own corpus (the bodies fill on cue via `crystal_recall`)