Koskamo

Vocenya Docs MCP

A read-only MCP server that allows AI agents to search Vocenya's developer documentation and API reference, returning endpoints and code samples without requiring authentication.

Visit Vocenya

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Vocenya Docs MCP logo, by VocenyaVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-06Operated by Vocenya
MCP endpoint (Streamable HTTP)
https://vocenya.com/mcp/docs
Vendor documentation

What its tools do

4 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Read-only (4)

4 of 4 have a description · 4 of 4 declare behavior hints · 4 of 4 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to vocenya.com ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Search developer documentation for API endpoints
  • Retrieve code samples for Vocenya API integration
  • Access public documentation via AI assistants

Source and maintenance

Vendor evidenceRegistry 1.0.0
mcp-registry: com.vocenya/docs@1.0.0Source repositoryProject website
Maintenance checked

Protocol and capabilities

Server
Vocenya Docs 1.0.0
MCP protocol negotiated in check
2025-11-25
Tools
4 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

The Vocenya developer docs (vocenya.com/docs): the REST API for a business's calls, leads, bookings, chats, outbound AI calls, Do Not Call list and webhooks, plus the live chat widget and the Vocenya MCP servers. Use these tools while writing an integration, so you use real endpoints, parameters, scopes and limits. Quote them rather than guessing; if something is not in the docs, say so instead of inventing an endpoint, field or event. - search_docs: find guides and endpoints by words (for example "verify webhook signature"). - get_doc_page: read a page as Markdown ("quickstart", "authentication", "webhooks", "webhook-events", "outbound-calls", "reference/leads"). - list_endpoints: every endpoint, optionally for one resource (tag). - get_endpoint: one endpoint in full, with code samples, by method and path. Requests authenticate with an organization API key: `Authorization: Bearer $VOCENYA_API_KEY`. Never ask the user to paste a key into the chat; tell them to set it as an environment variable. This server is read-only and cannot see any account; a business's own data is on the authenticated platform server at /mcp/platform.

Tools

4 advertised

search_docs — Search developer docs
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

search_docs input schema
{
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "maxLength": 200,
      "description": "Words to look for, like \"verify webhook signature\", \"pagination\" or \"create lead\"."
    }
  }
}
search_docs annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}
get_doc_page — Get docs page
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

get_doc_page input schema
{
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "maxLength": 200,
      "description": "The page slug, like \"webhooks\" or \"reference/leads\". A docs URL works too."
    }
  }
}
get_doc_page annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}
list_endpoints — List API endpoints
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

list_endpoints input schema
{
  "type": "object",
  "properties": {
    "tag": {
      "type": "string",
      "maxLength": 100,
      "description": "Optional resource name, like \"Leads\", \"Outbound calls\" or \"Do Not Call\"."
    }
  }
}
list_endpoints annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}
get_endpoint — Get API endpoint
Advertised by the server during the last successful anonymous check.
Advertised read-only

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

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

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
793 ms
95th percentile latency
793 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 793 ms · metadata changed · 4 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http vocenya-docs-mcp https://vocenya.com/mcp/docs

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add vocenya-docs-mcp --url https://vocenya.com/mcp/docs

Cursor

Merge this server into .cursor/mcp.json in your project, then enable vocenya-docs-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "vocenya-docs-mcp": {
      "url": "https://vocenya.com/mcp/docs"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "vocenya-docs-mcp": {
      "type": "streamableHttp",
      "url": "https://vocenya.com/mcp/docs",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start vocenya-docs-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "vocenya-docs-mcp": {
      "type": "http",
      "url": "https://vocenya.com/mcp/docs"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http vocenya-docs-mcp https://vocenya.com/mcp/docs

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://vocenya.com/mcp/docs

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "vocenya-docs-mcp": {
      "serverUrl": "https://vocenya.com/mcp/docs"
    }
  }
}

Let your agent find its tools

Find servers like Vocenya Docs MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 1,106

Do you run Vocenya Docs MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing