Anamnese vs Penfield MCP

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

A
AnamneseKnowledge & Memory
A self-improving memory layer. Your memory, notes, tasks and goals, remembered everywhere.37FairAuth: not declared
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

Verdict: choose Anamnese 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?

A
Choose Anamnese when

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

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.

Spec
A
Anamnese
Penfield MCP logoPenfield MCP
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal37/100 · Fair49/100 · Fair
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredOAuth 2.0
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars—6
Directory activity 0 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Anamnese 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.

Anamnese

No confirmed install command for Anamnese 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

Anamnese 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 Anamnese 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. Anamnese has no confirmed install command yet — follow its own setup instructions.

Anamnese has no declared pricing — check the project's own site. 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 anamnese and penfieldlabs-penfield-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

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