MCP Memory vs Engram MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
MCP Memory vs Engram MCP
In-depth architectural comparison of the MCP Memory and Engram MCP 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
MCP Memory
Knowledge & Memory · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Engram MCP
Knowledge & Memory · Local stdio
Quality: 42/100 (Fair) | Auth: No auth required
Verdict Summary: Choose MCP Memory if you need specialized Knowledge & Memory tools running via a local process. Choose Engram MCP 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 MCP 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).
Smart memory with exponential decay. Memories strengthen on access and fade when unused — solving the Karpathy problem of unbounded context growth. 7 tools, SQLite-based, zero dependencies.
Persistent semantic memory for AI agents. SQLite-backed, local-first, zero config. Semantic search via Ollama embeddings (nomic-embed-text) with keyword fallback. remember, recall, history, forget, and stats tools. Works with Claude Desktop, Cursor, and any MCP client.
Category & Scope
Tools & Capabilities Breakdown
MCP Memory Tools (4)
remember
Store a memory. Auto-categorizes from content. Auto-deduplicates via bigram similarity. Supersedes conflicting preferences.
recall
Retrieve memories ranked by relevance. Auto-reinforces top match. Auto-prunes dead memories.
forget
Delete a memory by ID or fuzzy content match.
inspect
Debug view: all memories with decay status, relevance scores, category breakdown, health.
Engram MCP Tools (11)
remember
Store a new memory with automatic entity extraction, theme detection, and relationship mapping.
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).
MCP Memory is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Engram MCP belongs to Knowledge & Memory using local stdio subprocess. Select MCP Memory when you need capabilities focused on knowledge & memory and Engram MCP when you require tools for knowledge & memory.