In-depth architectural comparison of the MCP Memory Graph 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
MCP Memory Graph
Knowledge & Memory · Local stdio
Quality: 37/100 (Fair) | Auth: No auth required
Scrivener MCP
Knowledge & Memory · Local stdio
Quality: 61/100 (Good) | Auth: No auth required
Verdict Summary: Choose MCP Memory Graph 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 MCP Memory Graph 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).
Authority-weighted memory graph for AI agents with conflict detection and semantic search.
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
MCP Memory Graph Tools (8)
store_memory
Store with conflict detection and optional auto-resolve
retrieve_memories
Semantic search ranked by similarity × authority
check_conflicts
Preview conflicts before storing
update_memory
Update content/priority with supersession tracking
delete_memory
Soft delete (preserves history)
add_memory_edge
Manually add typed relationship
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).
MCP Memory Graph is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Scrivener MCP belongs to Knowledge & Memory using local stdio subprocess. Select MCP Memory Graph when you need capabilities focused on knowledge & memory and Scrivener MCP when you require tools for knowledge & memory.