In-depth architectural comparison of the Penfield MCP and Tokenmizer 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: 44/100 (Fair) | Auth: OAuth 2.0
Tokenmizer
Knowledge & Memory · Local stdio
Quality: 56/100 (Good) | Auth: API Key required
Verdict Summary: Choose Penfield MCP if you need specialized Knowledge & Memory tools running via a local process. Choose Tokenmizer 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: OAuth 2.0 (Free / Open Source).
Primary tools included: Persistent memory across sessions, Hybrid BM25, vector, and graph search, Knowledge graph with 24 relationship types.
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.
Graph-structured session memory for LLMs. Local OpenAI-compatible proxy that extracts tasks, decisions, and files into a typed knowledge graph, auto-checkpoints before context overflow, and resumes any session in 250 tokens. 6 MCP tools including whydecision (traces why a decision changed, with reasons and evidence). pip install tokenmizer
Category & Scope
Tools & Capabilities Breakdown
Penfield MCP Tools (6)
Persistent memory across sessions
Hybrid BM25, vector, and graph search
Knowledge graph with 24 relationship types
Context save and restore checkpoints
Artifact storage and retrieval
OAuth-authenticated hosted MCP endpoint
Tokenmizer Tools (6)
Typed graph memory for decisions, tasks, files, errors, and goals
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, Tokenmizer belongs to Knowledge & Memory using local stdio subprocess. Select Penfield MCP when you need capabilities focused on knowledge & memory and Tokenmizer when you require tools for knowledge & memory.