Claude Engram vs Context Memory — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Claude Engram vs Context Memory
In-depth architectural comparison of the Claude Engram and Context 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
Claude Engram
Knowledge & Memory · Local stdio
Quality: 49/100 (Fair) | Auth: No auth required
Context Memory
Knowledge & Memory · Local stdio
Quality: 37/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Claude Engram if you need specialized Knowledge & Memory tools running via a local process. Choose Context 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?
Choose Claude Engram 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).
Primary tools included: Persistent local memory for Claude Code, Automatic hook-based event capture, Cross-session history mining and search.
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).
Primary tools included: SQLite FTS5 full-text search with Porter stemming, Two-tier summary and deep-content retrieval, Project-scoped and global search.
Persistent memory and session intelligence for Claude Code. Auto-tracks mistakes, decisions, and context via hooks. Mines session history for patterns and cross-session search. Loop detection, pre-edit warnings, context compaction survival. Runs locally with Ollama.
Persistent, searchable context storage across Claude Code sessions using SQLite FTS5. Save sessions with AI-generated summaries, two-tier full-text search, checkpoint recovery, and a web dashboard.
Category & Scope
Tools & Capabilities Breakdown
Claude Engram Tools (6)
Persistent local memory for Claude Code
Automatic hook-based event capture
Cross-session history mining and search
Compaction checkpoints and recovery
Dependency and edit-impact analysis
Local Ollama and embedding support
Context Memory Tools (6)
SQLite FTS5 full-text search with Porter stemming
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).
Claude Engram is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Context Memory belongs to Knowledge & Memory using local stdio subprocess. Select Claude Engram when you need capabilities focused on knowledge & memory and Context Memory when you require tools for knowledge & memory.