In-depth architectural comparison of the Scrivener MCP and Context First 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
Scrivener MCP
Knowledge & Memory · Local stdio
Quality: 61/100 (Good) | Auth: No auth required
Context First MCP
Knowledge & Memory · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Verdict Summary: Choose Scrivener MCP if you need specialized Knowledge & Memory tools running via a local process. Choose Context First 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 Scrivener 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).
Primary tools included: Scrivener 3 document access and editing, Deterministic writing analysis, Keyword and offline semantic search.
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
Session memory, context health monitoring, reasoning quality, and truthfulness verification MCP server with 37 tools and tiered memory storage. npx -y context-first-mcp
Category & Scope
Tools & Capabilities Breakdown
Scrivener MCP Tools (6)
Scrivener 3 document access and editing
Deterministic writing analysis
Keyword and offline semantic search
Character, plot, and project memory tracking
AI-assisted generation and content enhancement
Progressive skill loading
Context First MCP Tools (36)
context_loop
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).
Scrivener MCP is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Context First MCP belongs to Knowledge & Memory using local stdio subprocess. Select Scrivener MCP when you need capabilities focused on knowledge & memory and Context First MCP when you require tools for knowledge & memory.
One-call orchestrator.** Runs 8 stages (ingest→recap→conflict→ambiguity→entropy→abstention→discovery→synthesis) and returns a single `directive` with `action`, `contextHealth` score, extracted facts, and suggested next tools
recap_conversation
Extracts hidden intent, key decisions, and produces consolidated state summaries
detect_conflicts
Compares new input against ground truth; surfaces contradictions
check_ambiguity
Identifies underspecified requirements and generates clarifying questions
verify_execution
Validates whether tool outputs actually achieved the stated goal
entropy_monitor
Proxy-entropy scoring via lexical diversity, contradiction density, hedge frequency, and n-gram repetition (ERGO)
abstention_check
5-dimension confidence scoring — abstains with questions rather than hallucinating (RLAAR)
detect_drift
Detects conversation drift from the original intent
check_depth
Evaluates response depth against question complexity
get_state
Retrieve confirmed facts and task status
set_state
Lock in ground truth — subsequent conflict checks run against these values