Vocenya Docs vs Scrivener MCP
A side-by-side look at the Vocenya Docs 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 Vocenya Docs for developer tools work over a hosted endpoint; choose Scrivener MCP for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Vocenya Docs when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
- You want tools like
search_docs, get_doc_page, list_endpoints.
Choose Scrivener MCP when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Knowledge & Memory |
| Quality signal | 76/100 · Great | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Verified | Community listing |
| GitHub stars | — | 67 |
| Directory activity | 2 views 0 installs 0 upvotes | 18 views 12 installs 6 upvotes |
| Tools | 4 | Not listed |
| Full listing | View Vocenya Docs | View Scrivener MCP |
Tools & capabilities
Vocenya Docs tools 4
search_docsSearch the Vocenya developer docs: guides (authentication, webhooks, pagination, outbound calling rules, live chat, MCP) and every API endpoint. Returns the best matches with their page URL; read one with get_doc_page or get_endpoint.get_doc_pageGet one page of the Vocenya developer docs as Markdown, exactly as published. Slugs: "index", a guide like "quickstart", "authentication", "webhooks", "webhook-events", "outbound-calls", "live-chat" or "mcp", "reference" for the API overview, or "reference/leads" for a resource's endpoints. Use search_docs to find a slug.list_endpointsList the endpoints of the Vocenya REST API with their method, path, summary and required scope, grouped by resource. Pass a tag (resource) like "Leads" or "Webhooks" to list one resource. Get the details of one with get_endpoint.get_endpointGet one Vocenya API endpoint in full, as Markdown: its scope, path and query parameters, request body, responses, response attributes and code samples in cURL, Node, PHP and Python. Example: method "POST", path "/leads".
Scrivener MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
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.
Vocenya Docs
{
"mcpServers": {
"vocenya-docs": {
"url": "https://vocenya.com/mcp/docs"
}
}
}
Scrivener MCP
{
"mcpServers": {
"writerslogic-scrivener-mcp": {
"command": "npx",
"args": [
"-y",
"scrivener-setup"
]
}
}
}
Frequently asked questions
Vocenya Docs is categorized under Developer Tools and uses a remote HTTP/SSE transport. Scrivener MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Vocenya Docs for developer tools work and Scrivener MCP for knowledge & memory.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Vocenya Docs is listed as free. Auth: no auth required. Scrivener MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add vocenya-docs and writerslogic-scrivener-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Vocenya Docs has a quality signal of 76/100 (Great) with 2 views, 0 installs and 0 GitHub stars. Scrivener MCP has 61/100 (Good) with 18 views, 12 installs and 67 GitHub stars.