Claude Engram vs Cortex Plugin — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Claude Engram vs Cortex Plugin
In-depth architectural comparison of the Claude Engram and Cortex Plugin 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
Cortex Plugin
Knowledge & Memory · Local stdio
Quality: 60/100 (Good) | Auth: No auth required
Verdict Summary: Choose Claude Engram if you need specialized Knowledge & Memory tools running via a local process. Choose Cortex Plugin 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).
You have access to required keys: MEMEM_TELEMETRY_SOURCE.
Primary tools included: Event-triggered background miner extracting durable lessons from conversations, Stores memories as markdown files in a local Obsidian vault, Active Memory Slice assembling query-tailored context briefings.
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, self-evolving memory plugin for Claude Code. Background miner extracts durable lessons (decisions, conventions, bug fixes) from completed sessions via Claude Haiku, stores them as human-readable markdown in an Obsidian vault, and assembles query-tailored context briefings at session start. Local-first, no cloud, no API keys. Self-healing install via uv bootstrap shim, /cortex-doctor preflight, graceful FTS-only degraded mode when claude CLI missing. MIT.
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
Cortex Plugin Tools (6)
Event-triggered background miner extracting durable lessons from conversations
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, Cortex Plugin belongs to Knowledge & Memory using local stdio subprocess. Select Claude Engram when you need capabilities focused on knowledge & memory and Cortex Plugin when you require tools for knowledge & memory.