Vocenya Docs

Read-only search over the Vocenya AI receptionist API docs and endpoints, with code samples.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
97%
Naming quality
100%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~569Tokens (tool definitions)
~643 BTypical response size
Minimal attention impact (0.44% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "docs": {
      "url": "https://vocenya.com/mcp/docs"
    }
  }
}

Remote endpoints

https://vocenya.com/mcp/docsstreamable-http

What it can do

Tool inventory

Tools (4)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢search_docs(query)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "description": "Words to look for, like \"verify webhook signature\", \"pagination\" or \"create lead\".",
      "maxLength": 200,
      "type": "string"
    }
  },
  "required": [
    "query"
  ]
}
🟢get_doc_page(slug)

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 overview, or "reference/leads" for a resource's endpoints. Use search_docs to find a slug.

Input Schema

{
  "type": "object",
  "properties": {
    "slug": {
      "description": "The page slug, like \"webhooks\" or \"reference/leads\". A docs URL works too.",
      "maxLength": 200,
      "type": "string"
    }
  },
  "required": [
    "slug"
  ]
}
🟢list_endpoints(tag)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "tag": {
      "description": "Optional resource name, like \"Leads\", \"Outbound calls\" or \"Do Not Call\".",
      "maxLength": 100,
      "type": "string"
    }
  }
}
🟢get_endpoint(method, path)

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".

Input Schema

{
  "type": "object",
  "properties": {
    "method": {
      "description": "The HTTP method.",
      "enum": [
        "GET",
        "POST",
        "PUT",
        "PATCH",
        "DELETE"
      ],
      "type": "string"
    },
    "path": {
      "description": "The path, like \"/leads/{lead}\" (a concrete id like \"/leads/42\" works too).",
      "maxLength": 300,
      "type": "string"
    }
  },
  "required": [
    "method",
    "path"
  ]
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded4 tools