IWE vs Penfield MCP

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

IWE logoIWEKnowledge & MemoryMarkdown knowledge base as agent memory. Runs against the notes directory it is started in.44FairAuth: no auth requiredPenfield 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

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

Which MCP server should you choose?

IWE logoChoose IWE when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • Its auth model fits you: No auth required.
Explore IWE

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecIWE logoIWEPenfield MCP logoPenfield MCP
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal44/100 · Fair49/100 · Fair
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNo auth requiredOAuth 2.0
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars1,7856
Directory activity 2 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

IWE tools

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

Penfield MCP 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.

IWE

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

Penfield MCP

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

Frequently asked questions

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

IWE has no declared pricing — check the project's own site. Auth: no auth required. Penfield MCP is listed as free. Auth: oauth 2.0. 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 iwe and penfieldlabs-penfield-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

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