In-depth architectural comparison of the Swarm Rd Orchestrator 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
Swarm Rd Orchestrator
Knowledge & Memory · Local stdio
Quality: 41/100 (Fair) | Auth: No auth required
Scrivener MCP
Knowledge & Memory · Local stdio
Quality: 61/100 (Good) | Auth: No auth required
Verdict Summary: Choose Swarm Rd Orchestrator 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 Swarm Rd Orchestrator 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: Three typed MCP tools over stdio, SQLite WAL-backed append-only event log, Ray actor-based concurrent coordination.
Append-only event log for cross-agent context/memory sharing via 3 MCP tools.
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
Swarm Rd Orchestrator Tools (6)
Three typed MCP tools over stdio
SQLite WAL-backed append-only event log
Ray actor-based concurrent coordination
Cursor-based event retrieval
Structured JSON CLI output
Input validation before storage
Scrivener MCP Tools (6)
Scrivener 3 document access and editing
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).
Swarm Rd Orchestrator is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Scrivener MCP belongs to Knowledge & Memory using local stdio subprocess. Select Swarm Rd Orchestrator when you need capabilities focused on knowledge & memory and Scrivener MCP when you require tools for knowledge & memory.