Context Keeper vs Mengram — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Context Keeper vs Mengram
In-depth architectural comparison of the Context Keeper and Mengram 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
Mengram
Knowledge & Memory · Local stdio
Quality: 59/100 (Good) | Auth: API Key required
Verdict Summary: Choose Context Keeper if you need specialized Knowledge & Memory tools running via a hosted cloud SSE transport. Choose Mengram 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).
Human-like memory layer for AI agents with semantic, episodic, and procedural memory. Claude Code hooks (auto-save, auto-recall, cognitive profile). 29 MCP tools, knowledge graph, smart triggers, multi-user isolation. Python & JS SDKs.
Category & Scope
Tools & Capabilities Breakdown
Context Keeper Tools (6)
Vector, timeline, and knowledge-graph retrieval
LLM-driven broad recall and precise reranking
Short-term and long-term memory layers
Session, user, and workspace isolation
Conversation storage and file association tools
HTTP, WebSocket, and SSE MCP support
Mengram Tools (6)
Semantic, episodic, and procedural memory
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).
Context Keeper is categorized under Knowledge & Memory and uses a remote streaming HTTP/SSE transport. In contrast, Mengram belongs to Knowledge & Memory using local stdio subprocess. Select Context Keeper when you need capabilities focused on knowledge & memory and Mengram when you require tools for knowledge & memory.