Cogmemai MCP vs Scrivener MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Cogmemai MCP vs Scrivener MCP
In-depth architectural comparison of the Cogmemai MCP 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
Cogmemai MCP
Knowledge & Memory · Local stdio
Quality: 61/100 (Good) | Auth: API Key required
Scrivener MCP
Knowledge & Memory · Local stdio
Quality: 61/100 (Good) | Auth: No auth required
Verdict Summary: Choose Cogmemai MCP 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 Cogmemai MCP when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
You have access to required keys: COGMEMAI_API_KEY.
Persistent cognitive memory for Claude Code. Cloud-first with semantic search, AI-powered extraction, and project scoping. Zero local databases.
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
Cogmemai MCP Tools (35)
preflight
Proactive recall.** Fast recall to check prior context before making any suggestion
save_memory
Store a fact explicitly (architecture decision, preference, etc.)
recall_memories
Search memories using natural language (semantic search)
extract_memories
Ai extracts facts from a conversation exchange automatically
get_project_context
Load top memories at session start (with smart ranking, health score, and session replay)
list_memories
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).
Cogmemai MCP is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Scrivener MCP belongs to Knowledge & Memory using local stdio subprocess. Select Cogmemai MCP when you need capabilities focused on knowledge & memory and Scrivener MCP when you require tools for knowledge & memory.