Brain MCP vs Penfield MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Brain MCP vs Penfield MCP
In-depth architectural comparison of the Brain MCP and Penfield MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Brain MCP
Knowledge & Memory · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Penfield MCP
Knowledge & Memory · Local stdio
Quality: 49/100 (Fair) | Auth: OAuth 2.0
Verdict Summary: Choose Brain MCP if you need specialized Knowledge & Memory tools running via a local process. Choose Penfield MCP if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
B
Choose Brain MCP when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Your Obsidian vault as private, searchable memory for Claude, Cursor, Hermes and any MCP client
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.
Persona bundle: profile note, memory notes, facts captured with `brain_remember`, skills, project list and recent focus. The server instructions ask clients to call this first. Pass `topic` for a smaller bundle.
brain_context
The sections most relevant to a question, with source note ids and a coverage label, from the hybrid ranker, packed under a size budget. Says so explicitly when the vault does not record the answer.
brain_search
Hybrid search (keywords, meaning, reranker, spelling correction) with project, type, topic and date filters. Returns ranked notes with snippets.
brain_read
One note, or one section of it, with metadata, topics and resolved links.
brain_project
Briefing on a project: description, latest progress, decisions, recent changes and notes grouped by type. With no argument it lists projects.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Brain MCP is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Penfield MCP belongs to Knowledge & Memory using local stdio subprocess. Select Brain MCP when you need capabilities focused on knowledge & memory and Penfield MCP when you require tools for knowledge & memory.
Links out, backlinks grouped by project, and notes that share topics.
brain_recent
Notes modified in the last N days, newest first.
brain_capture
Writes a new note with graph-ready frontmatter into the capture folder.
brain_remember
Appends a fact to the memory file; it joins `brain_identity` straight away. Near duplicates are refused (token Jaccard ≥ 0.6 or containment ≥ 0.85), partial overlaps get a `Supersedes` line, and `force=true` overrides.
brain_write
Creates a note at a chosen path in a writable folder (`Notes/` and the capture folder by default), or replaces one with `overwrite=true`. A `hub` note groups every note whose `project` matches its title.
brain_edit
Changes part of a note in one of three ways: replace text that matches once, replace a section under a heading, or append. Keeps the file's line endings and bumps `modified`.
brain_move
Moves or renames a note within the writable folders. Never overwrites, and names any notes whose links stop resolving.