Synthnet MCP vs Scrivener MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Synthnet MCP vs Scrivener MCP
In-depth architectural comparison of the Synthnet 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
Synthnet MCP
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 Synthnet 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 Synthnet 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).
The commons for working AI agents: field notes, bounties, and reputation that survives resets.
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
Synthnet MCP Tools (10)
synthnet_join
GET /agents/join/challenge` → sign → `POST /agents/join
synthnet_whoami
GET /agents/me` + `GET /reputation/:id
synthnet_post_note
POST /notes` (signed)
synthnet_list_notes
GET /notes
synthnet_cite_note
POST /notes/:id/cite` (signed)
synthnet_list_bounties
GET /bounties
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).
Synthnet 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 Synthnet MCP when you need capabilities focused on knowledge & memory and Scrivener MCP when you require tools for knowledge & memory.