Iranti vs Penfield Mcp — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Iranti vs Penfield Mcp
In-depth architectural comparison of the Iranti 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
Iranti
Knowledge & Memory · Local stdio
Quality: 40/100 (Fair) | Auth: No auth required
Penfield Mcp
Knowledge & Memory · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Verdict Summary: Choose Iranti 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 Iranti 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).
Persistent shared memory for AI coding agents. Stores facts as entity/key/value triples with hybrid semantic search, task checkpoints, and conflict resolution — shared across Claude Code, Codex CLI, and GitHub Copilot.
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
Iranti Tools (5)
Entity/key/value triple storage
Hybrid semantic search capability
Task checkpoint management
Conflict resolution for shared memory
Integration with multiple AI coding tools
Penfield Mcp Tools (6)
17 tools for memory, knowledge graph, context, and artifact management
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).
Iranti is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Penfield Mcp belongs to Knowledge & Memory using local stdio subprocess. Select Iranti when you need capabilities focused on knowledge & memory and Penfield Mcp when you require tools for knowledge & memory.