BovedIA vs Scrivener MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
BovedIA vs Scrivener MCP
In-depth architectural comparison of the BovedIA 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
BovedIA
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 BovedIA 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 BovedIA 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: Context loading controlled by a router note to load only relevant data, Notes stored as plain Markdown files on disk without databases, Supports cloud sync via iCloud, OneDrive, Google Drive, Dropbox, or local folders.
BovedIA is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Scrivener MCP belongs to Knowledge & Memory using local stdio subprocess. Select BovedIA when you need capabilities focused on knowledge & memory and Scrivener MCP when you require tools for knowledge & memory.
Personal memory for Claude Code in plain Markdown notes you own. Doesn't load context blindly: a router note decides what to load and when, plus an "alma" (soul) layer for what you think and feel, not just tasks. npx bovedia
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