GoodMemory vs Scrivener MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
GoodMemory vs Scrivener MCP
In-depth architectural comparison of the GoodMemory 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
GoodMemory
Knowledge & Memory · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Scrivener MCP
Knowledge & Memory · Local stdio
Quality: 61/100 (Good) | Auth: No auth required
Verdict Summary: Choose GoodMemory 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 GoodMemory 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: Durable memory API with remember, recall, feedback, forget, and export, Local-first storage using SQLite by default, with optional Postgres support, Read-only recall and inspection tools including trace and stats.
Local-first, auditable memory layer for Codex, Claude Code, and MCP clients. Stores scoped user/project memory in SQLite or Postgres, exposes read-only recall, trace, stats, and artifact tools by default, and supports opt-in governed writeback with review, forget, and audit controls. Published as io.github.hjqcan/goodmemory in the official MCP Registry.
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
Tools & Capabilities Breakdown
GoodMemory Tools (6)
Durable memory API with remember, recall, feedback, forget, and export
Local-first storage using SQLite by default, with optional Postgres support
Read-only recall and inspection tools including trace and stats
Opt-in governed writeback with review, forget, and audit controls
Integration hooks for Codex and Claude Code agent hosts
TypeScript declarations and compiled artifacts for SDK and HTTP usage
Scrivener MCP Tools (6)
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).
GoodMemory is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Scrivener MCP belongs to Knowledge & Memory using local stdio subprocess. Select GoodMemory when you need capabilities focused on knowledge & memory and Scrivener MCP when you require tools for knowledge & memory.