Context7 vs Scrivener MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Context7 vs Scrivener MCP
In-depth architectural comparison of the Context7 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
Context7
Knowledge & Memory · Local stdio
Quality: 65/100 (Great) | Auth: API Key required
Scrivener MCP
Knowledge & Memory · Local stdio
Quality: 61/100 (Good) | Auth: No auth required
Verdict Summary: Choose Context7 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 Context7 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).
Up-to-date code documentation for LLMs and AI code editors.
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
Context7 Tools (2)
resolve-library-id
Resolves a general library name into a Context7-compatible library ID.
query-docs
Retrieves documentation for a library using a Context7-compatible library ID.
Scrivener MCP Tools (6)
Scrivener 3 document access and editing
Deterministic writing analysis
Keyword and offline semantic search
Character, plot, and project memory tracking
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).
Context7 is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Scrivener MCP belongs to Knowledge & Memory using local stdio subprocess. Select Context7 when you need capabilities focused on knowledge & memory and Scrivener MCP when you require tools for knowledge & memory.