Connect Vocenya Docs and your agent gets 4 tools, among them get_doc_page, get_endpoint, list_endpoints. It answers at https://vocenya.com/mcp/docs over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 5 October 2026; the last check, on 21 November 2026, succeeded.
Read-only search over the Vocenya AI receptionist API docs and endpoints, with code samples.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
get_doc_page | Get 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 overvie Inputs: slug |
get_endpoint | Get 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". Inputs: method, path |
list_endpoints | List 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. Inputs: tag |
search_docs | Search 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. Inputs: query |
Every block below points at https://vocenya.com/mcp/docs. Pick your client and copy.
claude mcp add --transport http vocenya-docs https://vocenya.com/mcp/docs
{
"mcpServers": {
"vocenya-docs": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://vocenya.com/mcp/docs"]
}
}
}{
"mcpServers": {
"vocenya-docs": {
"url": "https://vocenya.com/mcp/docs"
}
}
}{
"servers": {
"vocenya-docs": {
"type": "http",
"url": "https://vocenya.com/mcp/docs"
}
}
}{
"context_servers": {
"vocenya-docs": {
"url": "https://vocenya.com/mcp/docs"
}
}
}{
"mcpServers": {
"vocenya-docs": {
"serverUrl": "https://vocenya.com/mcp/docs"
}
}
}{
"mcpServers": {
"vocenya-docs": {
"url": "https://vocenya.com/mcp/docs"
}
}
}name: Vocenya Docs
version: 0.0.1
schema: v1
mcpServers:
- name: Vocenya Docs
type: streamable-http
url: https://vocenya.com/mcp/docs{
"mcpServers": {
"vocenya-docs": {
"httpUrl": "https://vocenya.com/mcp/docs"
}
}
}{
"mcpServers": {
"vocenya-docs": {
"type": "http",
"url": "https://vocenya.com/mcp/docs"
}
}
}{
"mcpServers": {
"vocenya-docs": {
"url": "https://vocenya.com/mcp/docs"
}
}
}goose://extension?url=https%3A%2F%2Fvocenya.com%2Fmcp%2Fdocs&type=streamable_http&id=vocenya-docs&name=Vocenya%20Docs
It answered our last check on 21 November 2026 in 398 ms. Over 4 checks since 5 October 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by vocenya.com and served from vocenya.com, the vendor's own domain: https://vocenya.com/mcp/docs.
4, as returned by the server's own tools/list on 21 November 2026: get_doc_page, get_endpoint, list_endpoints, search_docs.
It answered our last check on 21 November 2026 in 398 ms. Over 4 checks since 5 October 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://vocenya.com/mcp/docs. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.vocenya. Endpoint host: vocenya.com. ARD identifier: urn:air:com.vocenya:mcp:docs.
First indexed 4 October 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.