In-depth architectural comparison of the Central Memory MCP 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
Central Memory MCP
Knowledge & Memory · Local stdio
Quality: 41/100 (Fair) | Auth: No auth required
Scrivener MCP
Knowledge & Memory · Local stdio
Quality: 61/100 (Good) | Auth: No auth required
Verdict Summary: Choose Central Memory MCP 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 Central Memory 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: Workspace-isolated entity and relation storage, Entity upserts that preserve existing IDs by name, Relation upserts using GUIDs or resolvable entity names.
An Azure PaaS-hostable MCP server that provides a workspace-grounded knowledge graph for multiple developers using Azure Functions MCP triggers and Table storage.
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
Category & Scope
Tools & Capabilities Breakdown
Central Memory MCP Tools (6)
Workspace-isolated entity and relation storage
Entity upserts that preserve existing IDs by name
Relation upserts using GUIDs or resolvable entity names
Observation storage with list conversion on read
HTTP health and readiness endpoints
Azure Table Storage data model
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).
Central Memory MCP is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Scrivener MCP belongs to Knowledge & Memory using local stdio subprocess. Select Central Memory MCP when you need capabilities focused on knowledge & memory and Scrivener MCP when you require tools for knowledge & memory.