Vocenya Docs logo

Vocenya Docs

Read-only MCP access to Vocenya API guides, endpoint references, scopes, parameters, responses, and code samples.

Install Vocenya Docs

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
Server URL
https://vocenya.com/mcp/docs

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Hosted endpointLive · 8h agoLive Remote EndpointOur automated health check connected to this remote MCP endpoint successfully.Last checked 8h ago · Nov 18, 2026, 19:45 UTC

Clients with native remote MCP support can connect directly to this URL.

Remote endpoint
https://vocenya.com/mcp/docs

Overview

Vocenya Docs MCP server exposes the Vocenya developer documentation through read-only MCP tools. It can search guides and API references, retrieve Markdown pages, list REST endpoints, and return endpoint details with cURL, Node, PHP, and Python examples. Reach for it when an agent needs current Vocenya API instructions or implementation details without modifying data.

Use cases

  • Search Vocenya authentication and webhook guides
  • List REST endpoints for a Vocenya resource
  • Inspect required scopes and request parameters
  • Generate request examples in supported languages

Key features

  • Searches guides and API endpoints
  • Returns documentation pages as Markdown
  • Lists endpoints by resource
  • Shows scopes, parameters, requests, and responses
  • Provides cURL, Node, PHP, and Python samples

Tools4

What Vocenya Docs lets your agent do. Expand a tool for its parameters.

Verified live~478 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

10/10 checks healthy over the last 45d

What it can do

From the 4 tools this server returned when we ran it.

Makes network requests · 3Read-only tools · 4

Observed 2026-10-17 in an isolated sandbox. A description of reach, not a security audit.

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

MaintenanceActively maintainedStatus declared by the project or listing owner.
Availability100%Our rolling endpoint + install checks that succeeded.
Tools exposed4Callable tools this server registers over MCP.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How Vocenya Docs works

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.

Reviews1

5.01 rating
51
40
30
20
10

Frequently Asked Questions about Vocenya Docs

Vocenya Docs is an MCP server that connects agents to the public Vocenya developer documentation. Its main tools search guides and endpoints, read documentation pages, list REST endpoints, and retrieve full endpoint details with scopes, parameters, responses, and cURL, Node, PHP, and Python samples.

Use `search_docs` to find matching endpoint references, or use `list_endpoints` to browse endpoints grouped by resource. Pass a tag such as `Leads` or `Webhooks` to narrow the list, then call `get_endpoint` with the endpoint method and path for full details.

Call `get_doc_page` with the page slug. Use `search_docs` first if you do not know the slug; supported examples include `authentication`, `webhooks`, `quickstart`, `live-chat`, `mcp`, `reference`, and resource pages such as `reference/leads`.

No. The server is public and read-only and returns documentation, endpoint references, and code samples. It does not execute the documented REST calls or modify Vocenya data.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewVocenya Docs AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/vocenya-docs?style=directory)](https://allmcps.com/mcp/vocenya-docs)
HTML Embed
<a href="https://allmcps.com/mcp/vocenya-docs"><img src="https://allmcps.com/api/badge/vocenya-docs?style=directory" alt="Vocenya Docs on AllMCPs" /></a>