Graphpilot vs Scrivener MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Graphpilot vs Scrivener MCP
In-depth architectural comparison of the Graphpilot 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
Graphpilot
Knowledge & Memory · Local stdio
Quality: 56/100 (Good) | Auth: No auth required
Scrivener MCP
Knowledge & Memory · Local stdio
Quality: 61/100 (Good) | Auth: No auth required
Verdict Summary: Choose Graphpilot 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 Graphpilot 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: Local MCP server over stdio, TypeScript and JavaScript structural indexing, Caller, callee, symbol-location, and blast-radius queries.
Structural memory for coding agents. Indexes TypeScript/JavaScript repos and exposes callers, callees, blast-radius impact, and symbol locations over MCP — with file:line@sha evidence anchors and branch-aware differential impact — so agents answer "who calls X?" / "what breaks if I change X?" without re-reading files. Local-only, zero telemetry, Apache-2.0. npx @graphpilot-oss/graphpilot mcp
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
Graphpilot Tools (6)
Local MCP server over stdio
TypeScript and JavaScript structural indexing
Caller, callee, symbol-location, and blast-radius queries
File:line@sha evidence anchors
Branch-aware differential impact analysis
Worktree-aware separate indexes
Scrivener MCP Tools (6)
Scrivener 3 document access and editing
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).
Graphpilot is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Scrivener MCP belongs to Knowledge & Memory using local stdio subprocess. Select Graphpilot when you need capabilities focused on knowledge & memory and Scrivener MCP when you require tools for knowledge & memory.