Kremis vs Scrivener MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Kremis vs Scrivener MCP
In-depth architectural comparison of the Kremis 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
Kremis
Knowledge & Memory · Remote HTTP/SSE
Quality: 53/100 (Good) | Auth: No auth required
Scrivener MCP
Knowledge & Memory · Local stdio
Quality: 61/100 (Good) | Auth: No auth required
Verdict Summary: Choose Kremis if you need specialized Knowledge & Memory tools running via a hosted cloud SSE transport. 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 Kremis when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Deterministic graph engine in Rust, CLI, HTTP API, and MCP bridge, BLAKE3 hashing of full graph state.
Deterministic knowledge graph MCP server. Single binary, zero LLM/embedding calls in the bridge, BLAKE3 state hashing, canonical KREX export for byte-identical audit. Local-first via redb (ACID). Alpha.
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
Kremis Tools (6)
Deterministic graph engine in Rust
CLI, HTTP API, and MCP bridge
BLAKE3 hashing of full graph state
Canonical KREX binary export
Proof-carrying queries through KVQC certificates
ACID persistence with redb
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).
Kremis is categorized under Knowledge & Memory and uses a remote streaming HTTP/SSE transport. In contrast, Scrivener MCP belongs to Knowledge & Memory using local stdio subprocess. Select Kremis when you need capabilities focused on knowledge & memory and Scrivener MCP when you require tools for knowledge & memory.