Penfield MCP vs WorkingMemory

A side-by-side look at the Penfield MCP and WorkingMemory MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Penfield MCP logoPenfield MCPKnowledge & Memory · Local subprocess (stdio)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.49FairAuth: oauth 2.0
W
WorkingMemoryKnowledge & Memory · Remote HTTP/SSE
Persistent personal memory for AI assistants — save, search, and recall across every MCP client.39FairAuth: no auth required

Verdict: choose Penfield MCP for knowledge & memory work as a local process; choose WorkingMemory for knowledge & memory over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Penfield MCP logoChoose Penfield MCP when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: OAuth 2.0.
Explore Penfield MCP

W
Choose WorkingMemory when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: No auth required.
Explore WorkingMemory

Feature & specification comparison

Rows where the two servers differ are marked.

SpecPenfield MCP logoPenfield MCP
W
WorkingMemory
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal49/100 · Fair39/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthOAuth 2.0No auth required
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars6—
Directory activity 4 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Penfield MCP tools

No tool names declared yet. Check the project README from the listing page.

WorkingMemory tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Penfield MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "penfieldlabs-penfield-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote"
      ]
    }
  }
}

WorkingMemory

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "workingmemory": {
      "command": "npx",
      "args": [
        "-y",
        "workingmemory"
      ]
    }
  }
}

Frequently asked questions

Penfield MCP is categorized under Knowledge & Memory and uses a local stdio subprocess. WorkingMemory belongs to Knowledge & Memory and uses a remote HTTP/SSE transport. Pick Penfield MCP for knowledge & memory work and WorkingMemory for knowledge & memory.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Penfield MCP is listed as free. Auth: oauth 2.0. WorkingMemory has no declared pricing — check the project's own site. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add penfieldlabs-penfield-mcp and workingmemory as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Penfield MCP has a quality signal of 49/100 (Fair) with 4 views, 0 installs and 6 GitHub stars. WorkingMemory has 39/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.