Core vs Penfield MCP

In-depth architectural comparison of the Core 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?

C

Choose Core 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: omega_store, omega_query, omega_welcome.

Explore Core Details

Choose Penfield MCP when:

• You need dedicated capabilities in the Knowledge & Memory domain.
• You prefer remote streaming HTTP/SSE 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

Feature & Specification Comparison

Specification	C Core Knowledge & Memory	Penfield MCP penfieldlabs Knowledge & Memory
Summary	Persistent memory for AI coding agents. #1 on LongMemEval. 26 MCP tools. Local-first.	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	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": {
    "core-2": {
      "command": "uvx",
      "args": [
        "omega-memory"
      ]
    }
  }
}

{
  "mcpServers": {
    "penfieldlabs-penfield-mcp": {
      "url": "https://mcp.penfield.app"
    }
  }
}

Related MCP Server Comparisons