# Vocenya Docs [Verified owner] [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://vocenya.com/mcp/docs  
**Views:** 5  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/vocenya-docs

## Description
Public, read-only MCP server for the Vocenya API docs: search guides, read pages and get every REST endpoint with cURL, Node, PHP and Python samples.

## Tools
Capabilities this server exposes over MCP:

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

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What the Vocenya Docs MCP server does

The Vocenya Docs MCP server provides agents with read-only access to the Vocenya API documentation. Its content covers general guides and REST API references, including authentication, webhooks, webhook events, pagination, outbound calling rules, live chat, and MCP usage.

The service is intended for documentation lookup rather than API execution. It does not create, update, or delete Vocenya resources. An agent can use it to locate relevant documentation, inspect a published page, review the available REST endpoints, or retrieve implementation details for a specific endpoint.

## How it works

The Vocenya Docs MCP server exposes four MCP tools:

- `search_docs` finds relevant guides and API endpoints. Results include page URLs, which can then be used to retrieve more detail.
- `get_doc_page` returns a selected documentation page as Markdown. Supported page slugs include `index`, guide pages such as `quickstart`, `authentication`, `webhooks`, `webhook-events`, `outbound-calls`, `live-chat`, and `mcp`, plus `reference` and resource pages such as `reference/leads`.
- `list_endpoints` returns Vocenya REST endpoints grouped by resource, including each endpoint's HTTP method, path, summary, and required scope. A resource tag such as `Leads` or `Webhooks` can narrow the result.
- `get_endpoint` returns a complete endpoint reference, including scope, path, query parameters, request body, responses, response attributes, and code samples.

A typical lookup starts with `search_docs`. After finding a relevant slug or endpoint, the agent can call `get_doc_page` or `get_endpoint` for the full material. For endpoint discovery by resource, `list_endpoints` can be used directly.

## Tools and capabilities

The Vocenya Docs MCP server supports documentation workflows such as:

- Searching guides and endpoint references
- Reading published documentation in Markdown
- Listing endpoints for the entire API or one resource
- Inspecting required authorization scopes
- Reviewing query parameters, request bodies, and response structures
- Getting cURL, Node, PHP, and Python request examples

The Vocenya Docs MCP server is useful when generating an integration plan, checking an endpoint's required scope, or producing language-specific request code based on the documented API shape.

## Limitations and notes

The server is public and read-only. It provides documentation content and examples, but the listed tools do not execute Vocenya API requests or change Vocenya data. Endpoint details should be obtained with `get_endpoint` when an exact request or response format is needed.

Search results provide page URLs, while page retrieval requires the relevant slug. If the slug is unknown, use `search_docs` first. Resource filtering for `list_endpoints` uses tags such as `Leads` and `Webhooks`.

The Vocenya Docs MCP server documents the Vocenya API, so agents still need the appropriate Vocenya credentials and runtime configuration when implementing or sending requests outside this documentation service.

_Full upstream README: https://allmcps.com/mcp/vocenya-docs/readme_

