Penfield MCP vs Workledge

A side-by-side look at the Penfield MCP and Workledge 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
WorkledgeKnowledge & Memory
A growing notebook shared by every AI you use. Save in conversation, recall from any connected AI.37FairAuth: not declared

Verdict: choose Penfield MCP for knowledge & memory work as a local process; choose Workledge for knowledge & memory. 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 Workledge when

  • You need dedicated capabilities in the Knowledge & Memory domain.
Explore Workledge

Feature & specification comparison

Rows where the two servers differ are marked.

SpecPenfield MCP logoPenfield MCP
W
Workledge
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal49/100 · Fair37/100 · Fair
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthOAuth 2.0Not declared
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.

Workledge 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"
      ]
    }
  }
}

Workledge

No confirmed install command for Workledge yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

Penfield MCP is categorized under Knowledge & Memory and uses a local stdio subprocess. Workledge belongs to Knowledge & Memory and uses an install path we have not confirmed yet. Pick Penfield MCP for knowledge & memory work and Workledge 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. Workledge has no confirmed install command yet — follow its own setup instructions.

Penfield MCP is listed as free. Auth: oauth 2.0. Workledge has no declared pricing — check the project's own site. 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 workledge 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. Workledge has 37/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.