Mengram vs Context Keeper

In-depth architectural comparison of the Mengram and Context Keeper 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 Mengram when:

• You need dedicated capabilities in the Knowledge & Memory domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: API Key required (Freemium).
• Primary tools included: Semantic, episodic, and procedural memory, 29 MCP tools, Knowledge graph support.

Explore Mengram Details

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

Feature & Specification Comparison

Specification	Mengram alibaizhanov Knowledge & Memory	Context Keeper redleaves Knowledge & Memory
Summary
Category & Scope	Knowledge & Memory	Knowledge & Memory

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": {
    "alibaizhanov-mengram": {
      "command": "uvx",
      "args": [
        "mengram-ai"
      ]
    }
  }
}

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

Related MCP Server Comparisons