Penfield MCP vs Gingugu

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

Explore Penfield MCP Details

Choose Gingugu when:

• You need dedicated capabilities in the Knowledge & Memory domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: Local SQLite persistent memory, BM25 and semantic hybrid search, Namespaces and typed knowledge graph.

Explore Gingugu Details

Feature & Specification Comparison

Specification	Penfield MCP penfieldlabs Knowledge & Memory	Gingugu gingugu Knowledge & Memory
Summary	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.	Persistent memory for AI coding assistants. Local SQLite, no cloud. 16 MCP tools: store, recall, search, relate, consolidate, export, and credential vault (OS keychain). Typed memories with confidence lifecycle (verified/inferred/stale/deprecated), namespaces, knowledge graph, and hybrid BM25 + semantic search via fastembed ONNX. Works with Cursor, Windsurf, Claude, and any MCP client. pip install gingugu

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": {
    "penfieldlabs-penfield-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote"
      ]
    }
  }
}

{
  "mcpServers": {
    "gingugu-gingugu": {
      "command": "uvx",
      "args": [
        "gingugu"
      ]
    }
  }
}

Related MCP Server Comparisons