Amber vs Penfield MCP

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

Amber logoAmberKnowledge & Memory · Remote HTTP/SSELong-term memory for AI assistants. Hybrid retrieval, query expansion, auto-topics.40FairAuth: not declaredPenfield 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 Amber for knowledge & memory work over a hosted endpoint; 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?

Amber logoChoose Amber when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a remote HTTP/SSE transport.
Explore Amber

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.

SpecAmber logoAmberPenfield MCP logoPenfield MCP
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal40/100 · Fair49/100 · Fair
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNot declaredOAuth 2.0
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars16
Directory activity 0 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

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

Amber

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "amber-3": {
      "url": "https://mcp.ambermem.com"
    }
  }
}

Penfield MCP

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

Frequently asked questions

Amber is categorized under Knowledge & Memory and uses a remote HTTP/SSE transport. Penfield MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Amber 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.

Amber 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 amber-3 and penfieldlabs-penfield-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

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