Scrivener MCP vs Screenpipe — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Scrivener MCP vs Screenpipe
In-depth architectural comparison of the Scrivener MCP and Screenpipe 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
Screenpipe
Knowledge & Memory · Local stdio
Quality: 69/100 (Great) | Auth: API Key required
Verdict Summary: Choose Scrivener MCP if you need specialized Knowledge & Memory tools running via a local process. Choose Screenpipe 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
Local-first workflow memory for AI agents. screenpipe lets MCP clients search selected screen, audio, app, and meeting context and turn real work into cited notes, SOPs, workflow reports, and automation candidates.
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
Screenpipe Tools (6)
search_content
Search screen recordings, OCR text, and audio transcriptions
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, Screenpipe belongs to Knowledge & Memory using local stdio subprocess. Select Scrivener MCP when you need capabilities focused on knowledge & memory and Screenpipe when you require tools for knowledge & memory.