Memex vs Scrivener MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Memex vs Scrivener MCP
In-depth architectural comparison of the Memex 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
Memex
Knowledge & Memory · Local stdio
Quality: 63/100 (Good) | Auth: No auth required
Scrivener MCP
Knowledge & Memory · Local stdio
Quality: 61/100 (Good) | Auth: No auth required
Verdict Summary: Choose Memex 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 Memex 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).
Developer context continuity system. Watches your git repos and builds a temporal knowledge graph of modules, symbols, decisions, and open problems via Graphiti + Neo4j, then serves it to any AI coding agent over MCP. Every edge carries a validity window and a confidence score that decays over time. 12 tools across read and write. Install via npx -y stifler-memex-mcp. MIT licensed.
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
Memex Tools (12)
get_project_context
Session start. Returns a cluster-level briefing under 1500 tokens regardless of repo size
get_symbol_context
Before editing a function or class. Returns callers, callees, linked decisions
get_recent_decisions
Last N days of architectural decisions, optionally module-scoped
Memex is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Scrivener MCP belongs to Knowledge & Memory using local stdio subprocess. Select Memex when you need capabilities focused on knowledge & memory and Scrivener MCP when you require tools for knowledge & memory.