In-depth architectural comparison of the Context Keeper and MCP Memory Graph 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
Context Keeper
Knowledge & Memory · Remote HTTP/SSE
Quality: 51/100 (Good) | Auth: No auth required
MCP Memory Graph
Knowledge & Memory · Local stdio
Quality: 45/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Context Keeper if you need specialized Knowledge & Memory tools running via a hosted cloud SSE transport. Choose MCP Memory Graph 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 Context Keeper when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Vector, timeline, and knowledge-graph retrieval, LLM-driven broad recall and precise reranking, Short-term and long-term memory layers.
LLM-driven context and memory management with wide-recall + precise-reranking RAG architecture. Features multi-dimensional retrieval (vector/timeline/knowledge graph), short/long-term memory, and complete MCP support (HTTP/WebSocket/SSE).
Local-first memory for Claude Code and any MCP client: hybrid search + knowledge graph, $0/token.
Context Keeper is categorized under Knowledge & Memory and uses a remote streaming HTTP/SSE transport. In contrast, MCP Memory Graph belongs to Knowledge & Memory using local stdio subprocess. Select Context Keeper when you need capabilities focused on knowledge & memory and MCP Memory Graph when you require tools for knowledge & memory.