Mnemostack vs Penfield MCP

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

Explore Mnemostack Details

Choose Penfield MCP when:

• You need dedicated capabilities in the Knowledge & Memory domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: OAuth 2.0 (Free / Open Source).
• Primary tools included: Persistent memory across sessions, Hybrid BM25, vector, and graph search, Knowledge graph with 24 relationship types.

Feature & Specification Comparison

Specification	Mnemostack udjin-labs Knowledge & Memory	Penfield MCP penfieldlabs Knowledge & Memory
Summary	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]'	Penfield: persistent memory with hybrid search (BM25 + vector + graph), 24 relationship types for knowledge graphs, context checkpoints for cognitive handoff, artifact storage, and personality system. Works across Claude, Cursor, Windsurf, and any MCP client.
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": {
    "udjin-labs-mnemostack": {
      "command": "uvx",
      "args": [
        "mnemostack"
      ],
      "env": {
        "GEMINI_API_KEY": "YOUR_GEMINI_API_KEY_HERE"
      }
    }
  }
}

{
  "mcpServers": {
    "penfieldlabs-penfield-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote"
      ]
    }
  }
}

Related MCP Server Comparisons