Penfield Mcp vs Agentram Mcp — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Penfield Mcp vs Agentram Mcp
In-depth architectural comparison of the Penfield Mcp and Agentram 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
Penfield Mcp
Knowledge & Memory · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Agentram Mcp
Knowledge & Memory · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
Verdict Summary: Choose Penfield Mcp if you need specialized Knowledge & Memory tools running via a local process. Choose Agentram 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 Penfield 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).
Primary tools included: 17 tools for memory, knowledge graph, context, and artifact management, Hybrid search combining BM25, vector embeddings, and graph connections, 24 relationship types for rich knowledge graph construction.
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).
Primary tools included: Personal memory storage with agent ID and key, Shared namespaces for multi-agent memory collaboration, Text-based search across keys and values without embeddings.
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.
Persistent memory for AI agents through a simple key-value HTTP API. No vector database or embeddings required. Store, retrieve, search, and share memory across agents with shared namespaces and TTL support. npx -y agentram-mcp
Category & Scope
Tools & Capabilities Breakdown
Penfield Mcp Tools (6)
17 tools for memory, knowledge graph, context, and artifact management
Hybrid search combining BM25, vector embeddings, and graph connections
24 relationship types for rich knowledge graph construction
Context checkpointing with awaken and reflect tools for session continuity
Cross-platform synchronization across multiple MCP clients
Artifact storage with save, retrieve, list, and delete capabilities
Agentram Mcp Tools (6)
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).
Penfield Mcp is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Agentram Mcp belongs to Knowledge & Memory using local stdio subprocess. Select Penfield Mcp when you need capabilities focused on knowledge & memory and Agentram Mcp when you require tools for knowledge & memory.