A side-by-side look at the Getcoherence MCP and Scrivener MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Getcoherence MCP for customer data platforms work as a local process; choose Scrivener MCP for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
COHERENCE_API_TOKEN, COHERENCE_API_URL.chat_with_agent, list_modules, list_module_fields.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Customer Data Platforms | Knowledge & Memory |
| Quality signal | 53/100 · Good | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | COHERENCE_API_TOKENCOHERENCE_API_URL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 67 |
| Directory activity | 2 views 0 installs 0 upvotes | 18 views 12 installs 6 upvotes |
| Tools | 13 | Not listed |
| Full listing | View Getcoherence MCP | View Scrivener MCP |
chat_with_agentSend a message to a Coherence agent; the agent uses its own toolset (email, reminders, calendar, social, landing pages, approvals, etc.) and returns its responselist_modulesList CRM modules in the workspacelist_module_fieldsList fields on a module — useful before creating/updating recordslist_recordsList records in a module with search + paginationget_recordGet a single record by IDcreate_recordCreate a new recordupdate_recordUpdate a record's fieldsdelete_recordSoft-delete a record (recoverable from trash)list_outreach_itemsList blog articles, LinkedIn posts, emails, etc.get_outreach_itemGet a single outreach item, including its MDX contentcreate_outreach_itemCreate a new outreach itemupdate_outreach_bodyUpdate the MDX body of an outreach itemNo tool names declared yet. Check the project README from the listing page.
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
{
"mcpServers": {
"mcp-189": {
"command": "npx",
"args": [
"-y",
"@coherenceos/mcp-server"
],
"env": {
"COHERENCE_API_TOKEN": "YOUR_COHERENCE_API_TOKEN_HERE",
"COHERENCE_API_URL": "YOUR_COHERENCE_API_URL_HERE"
}
}
}
}
{
"mcpServers": {
"writerslogic-scrivener-mcp": {
"command": "npx",
"args": [
"-y",
"scrivener-setup"
]
}
}
}
