In-depth architectural comparison of the Memory MCP 1file 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
Memory MCP 1file
Knowledge & Memory · Local stdio
Quality: 49/100 (Fair) | Auth: No auth required
Scrivener MCP
Knowledge & Memory · Local stdio
Quality: 61/100 (Good) | Auth: No auth required
Verdict Summary: Choose Memory MCP 1file 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 Memory MCP 1file 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 semantic memory with embedded ONNX embeddings, Knowledge graph backed by PetGraph, Embedded SurrealDB storage.
A self-contained Memory server with single-binary architecture (embedded DB & models, no dependencies). Provides persistent semantic and graph-based memory for AI agents.
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
Memory MCP 1file Tools (6)
Local semantic memory with embedded ONNX embeddings
Knowledge graph backed by PetGraph
Embedded SurrealDB storage
Code indexing with symbol relationships
Hybrid retrieval using Reciprocal Rank Fusion
Single-binary Rust architecture
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).
Memory MCP 1file is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Scrivener MCP belongs to Knowledge & Memory using local stdio subprocess. Select Memory MCP 1file when you need capabilities focused on knowledge & memory and Scrivener MCP when you require tools for knowledge & memory.