Context Keeper vs Mnemostack

In-depth architectural comparison of the Context Keeper and Mnemostack 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.

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.

Explore Context Keeper Details

Choose Mnemostack when:

• You need dedicated capabilities in the Knowledge & Memory domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
• You have access to required keys: GEMINI_API_KEY.
• Primary tools included: Hybrid vector, BM25, temporal, and graph retrieval, Reciprocal rank fusion with multi-stage reranking, Qdrant-backed persistent storage.

Feature & Specification Comparison

Specification	Context Keeper redleaves Knowledge & Memory	Mnemostack udjin-labs Knowledge & Memory
Summary	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).	Durable hybrid memory for AI agents. Combines vector search, BM25, temporal retrieval, and optional Memgraph knowledge graph via reciprocal rank fusion. 6 MCP tools: health, search, answer, feedback, graphquery, graphaddtriple. Self-hosted with Qdrant backend. 82.5% strict accuracy on LoCoMo benchmark. pip install 'mnemostack[mcp]'
Category & Scope

Tools & Capabilities Breakdown

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).

{
  "mcpServers": {
    "redleaves-context-keeper": {
      "url": "http://localhost:8088/mcp"
    }
  }
}

{
  "mcpServers": {
    "udjin-labs-mnemostack": {
      "command": "uvx",
      "args": [
        "mnemostack"
      ],
      "env": {
        "GEMINI_API_KEY": "YOUR_GEMINI_API_KEY_HERE"
      }
    }
  }
}

Related MCP Server Comparisons