In-depth architectural comparison of the Agreements API Sdk 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
Agreements API Sdk
Agreements & Coordination · Local stdio
Quality: 56/100 (Good) | Auth: API Key required
Scrivener MCP
Knowledge & Memory · Local stdio
Quality: 61/100 (Good) | Auth: No auth required
Verdict Summary: Choose Agreements API Sdk if you need specialized Agreements & Coordination 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 Agreements API Sdk when:
You need dedicated capabilities in the Agreements & Coordination domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: SHODAI_API_KEY.
Primary tools included: Hosted Streamable HTTP MCP endpoint, Local stdio MCP server package, Agreement definition and validation.
Remote Streamable HTTP and local stdio MCP server for defining, validating, deploying, and operating machine-readable agreements with EIP-712 permit preparation, signed participant inputs, state reads, and input history.
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
Agreements API Sdk Tools (6)
Hosted Streamable HTTP MCP endpoint
Local stdio MCP server package
Agreement definition and validation
Deployment preflight and typed-data preparation
State, transitions, and input history
EIP-712 permit-signing helpers
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).
Agreements API Sdk is categorized under Agreements & Coordination and uses a local stdio subprocess. In contrast, Scrivener MCP belongs to Knowledge & Memory using local stdio subprocess. Select Agreements API Sdk when you need capabilities focused on agreements & coordination and Scrivener MCP when you require tools for knowledge & memory.