Vectr vs Scrivener MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Vectr vs Scrivener MCP
In-depth architectural comparison of the Vectr 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
Vectr
Knowledge & Memory · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
Scrivener MCP
Knowledge & Memory · Local stdio
Quality: 61/100 (Good) | Auth: No auth required
Verdict Summary: Choose Vectr 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 Vectr 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: AST-aware code chunking for semantic retrieval, Hybrid dense embeddings combined with BM25 ranking, Symbol and call graph for precise locate and trace operations.
Semantic codebase search + persistent working memory for AI code editors. Hybrid dense + BM25 search over AST-aware chunks, a symbol graph for locate/trace, and typed notes that survive context compaction and session restarts. Local embeddings, zero config, no API key. pip install vectr
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
Vectr Tools (6)
AST-aware code chunking for semantic retrieval
Hybrid dense embeddings combined with BM25 ranking
Symbol and call graph for precise locate and trace operations
Typed notes with trigger conditions for automatic delivery
Local embedding model with zero configuration and no API key
Persistent storage of notes surviving session restarts and compaction
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).
Vectr is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Scrivener MCP belongs to Knowledge & Memory using local stdio subprocess. Select Vectr when you need capabilities focused on knowledge & memory and Scrivener MCP when you require tools for knowledge & memory.