Mengram vs Penfield MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Mengram vs Penfield MCP
In-depth architectural comparison of the Mengram 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
Mengram
Knowledge & Memory · Local stdio
Quality: 59/100 (Good) | Auth: API Key required
Penfield MCP
Knowledge & Memory · Local stdio
Quality: 48/100 (Fair) | Auth: OAuth 2.0
Verdict Summary: Choose Mengram 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?
Choose Mengram when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
Human-like memory layer for AI agents with semantic, episodic, and procedural memory. Claude Code hooks (auto-save, auto-recall, cognitive profile). 29 MCP tools, knowledge graph, smart triggers, multi-user isolation. Python & JS SDKs.
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.
Category & Scope
Tools & Capabilities Breakdown
Mengram Tools (6)
Semantic, episodic, and procedural memory
29 MCP tools
Knowledge graph support
Claude Code, Codex, and Cursor lifecycle hooks
Multilingual retrieval across 23 languages
Cloud and local memory modes
Penfield MCP Tools (6)
Persistent memory across sessions
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).
Mengram is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Penfield MCP belongs to Knowledge & Memory using local stdio subprocess. Select Mengram when you need capabilities focused on knowledge & memory and Penfield MCP when you require tools for knowledge & memory.