Search Memory vs Penfield MCP

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

Search Memory logoSearch MemoryKnowledge & Memory · Local subprocess (stdio)Free web search and long-term memory for AI assistants. No API keys; data stays local.56GoodAuth: 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 Search Memory for knowledge & memory work as a local process; 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?

Search Memory logoChoose Search Memory when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like web_search, fetch_content, research.
Explore Search Memory

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.

SpecSearch Memory logoSearch MemoryPenfield MCP logoPenfield MCP
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal56/100 · Good49/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local 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
Tools12Not listed

Tools & capabilities

Search Memory tools 12

  • web_searchSearches the web and returns ranked results. Supports `strategy` (`fallback`/`aggregate`/`auto`), `domain`, `from_date`/`to_date`, `format` (`text`/`json`), and `deep=true` for source-backed answers.
  • fetch_contentFetches a URL and returns clean Markdown with content caching, charset handling, GitHub Raw fast paths, RSS feed extraction, and Playwright fallback.
  • researchResearches a question in one call: checks the local knowledge base, searches the web, reads the top pages (`max_sources`, default 3), answers with citations from both, and adds the pages it read to the knowledge base (`index=false` to skip; sources already indexed are not added again).
  • server_statusReturns provider availability, cache stats, knowledge index stats, memory stats, entity graph stats, recent search traces, browser state, routing profile metadata, feature flags, and uptime.
  • ingest_documentChunks a document and indexes it into the local knowledge base (FTS + vectors) and entity graph. Pass `content`, or `path` to a local PDF, DOCX, EPUB, HTML or text file inside `INGEST_ALLOWED_DIRS`.
  • index_urlFetches a URL and indexes its Markdown into the local knowledge base and entity graph.
  • search_indexHybrid keyword + semantic search over the local knowledge base; returns chunks with source citations. Supports `format: "json"`.
  • list_indexLists documents stored in the local knowledge base.
  • rememberStores a short fact or note in session memory.
  • recallSearches or lists session memory notes.
  • forgetDeletes a session memory note by id.
  • find_relatedExplores the entity graph: related documents and co-occurring entities for an entity name.

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.

Search Memory

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "search-memory": {
      "command": "npx",
      "args": [
        "-y",
        "search-memory-mcp@latest"
      ]
    }
  }
}

Penfield MCP

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

Frequently asked questions

Search Memory is categorized under Knowledge & Memory and uses a local stdio subprocess. Penfield MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Search Memory 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.

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

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