In-depth architectural comparison of the Conventions MCP 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
Conventions MCP
Knowledge & Memory · Local stdio
Quality: 45/100 (Fair) | Auth: No auth required
Scrivener MCP
Knowledge & Memory · Local stdio
Quality: 61/100 (Good) | Auth: No auth required
Verdict Summary: Choose Conventions MCP 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 Conventions MCP 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).
Memory for coding conventions and standing instructions that persists across sessions.
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
Conventions MCP Tools (7)
capture_thought
Save a convention, instruction, correction, or preference. Embeds locally; classification is provided by the calling agent.
update_thought
Correct/refine an existing thought in place — same id, re-embedded and re-tagged from the new content.
search_thoughts
Hybrid semantic + keyword search.
list_thoughts
List all captures, optionally filtered by type.
list_rules
Every global + current-project rule in one deterministic call — no embeddings, no ranking, ordered by id. What the hooks use under the hood.
thought_stats
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).
Conventions MCP is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Scrivener MCP belongs to Knowledge & Memory using local stdio subprocess. Select Conventions MCP when you need capabilities focused on knowledge & memory and Scrivener MCP when you require tools for knowledge & memory.