In-depth architectural comparison of the Agent Memory 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
Agent Memory MCP
Knowledge & Memory · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
Scrivener MCP
Knowledge & Memory · Local stdio
Quality: 61/100 (Good) | Auth: No auth required
Verdict Summary: Choose Agent Memory 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 Agent Memory 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).
Markdown memory for AI agents. Files you can read, edit, grep, and commit. Not a database.
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
Agent Memory MCP Tools (24)
save_memory
Create or update a memory. Atomic write + locked. Validates name + type. Updates the index.
search_memories
Fuzzy search (Fuse.js · typo-tolerant, word-order tolerant, partial matches). Returns top N with relevance 0-100 + body snippet.
relevant_memories
Same matching as search, but returns full memory bodies as one markdown doc. Built for LLM auto-context.
get_memory
Fetch one memory by name. Returns frontmatter + body.
list_memories
List memories. Optional `type` filter. Paginated (default 50/page).
delete_memory
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).
Agent Memory 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 Agent Memory MCP when you need capabilities focused on knowledge & memory and Scrivener MCP when you require tools for knowledge & memory.
Receipt-required, target-bound, single-use.** Pass a Compliance Receipt from `check_action({action:'delete memory <name>', action_type:'deletions'})` — bound to that exact memory (via the `action_hash` caveat) and usable once. Soft-deletes to `.trash/<ts>-<name>.md`.
restore_memory
Restore a soft-deleted memory from `.trash/`. Picks the most recent trash entry for the name.
doctor
Storage integrity check. Reports orphans, dangling index entries, unreadable files. Pass `rebuild-index=true` to repair `MEMORY.md` from disk.
stats
Dashboard: counts per type, total size, largest memory, audit-log size, trash count.
log_events
Read recent entries from the audit event log. Optional `tail` (default 20) + `action` filter.
verify_memory
Re-evaluate a memory's claims. Extracts URLs/dates/file refs, flags stale-date signals, returns type-specific verification heuristics. Pairs with the `audit_stale` prompt.
find_backlinks
List memories that link to the given memory via `[[wiki-link]]` syntax in their bodies. Useful for "what references this" views.