Tokenmizer vs Scrivener MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Tokenmizer vs Scrivener MCP
In-depth architectural comparison of the Tokenmizer and Scrivener 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
Tokenmizer
Knowledge & Memory · Local stdio
Quality: 56/100 (Good) | Auth: API Key required
Scrivener MCP
Knowledge & Memory · Local stdio
Quality: 61/100 (Good) | Auth: No auth required
Verdict Summary: Choose Tokenmizer if you need specialized Knowledge & Memory tools running via a local process. Choose Scrivener 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 Tokenmizer when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: TOKENMIZER_ANTHROPIC_API_KEY, TOKENMIZER_URL.
Primary tools included: Typed graph memory for decisions, tasks, files, errors, and goals, Session checkpoint and compact resume tools, Decision supersession tracing with reasons and evidence.
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
Connect Scrivener 3 writing projects to Claude and other AI assistants. 47 tools for document management, writing analysis, semantic search, character/plot memory, and content enhancement. Progressive skill loading, relationship engine with HMS triplets, and JS fallback for offline semantic search. npm i -g scrivener-mcp
Tools & Capabilities Breakdown
Tokenmizer Tools (6)
Typed graph memory for decisions, tasks, files, errors, and goals
Session checkpoint and compact resume tools
Decision supersession tracing with reasons and evidence
OpenAI-compatible local proxy
SQLite-backed graph and checkpoint storage
Token savings and graph statistics
Scrivener 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).
Tokenmizer is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Scrivener MCP belongs to Knowledge & Memory using local stdio subprocess. Select Tokenmizer when you need capabilities focused on knowledge & memory and Scrivener MCP when you require tools for knowledge & memory.