Vocenya

com.vocenyav1.1.0Updated Oct 5, 2026

Calls, leads, bookings, chats, outbound AI calls and Do Not Call for one Vocenya business.

Overview

AI-generated overview

Lets an assistant read and act on one Vocenya business account's calls, leads, bookings and chats, and queue outbound AI calls.

What it does
The platform server exposes one Vocenya business account: list and get calls (with AI summary and transcript unless the account is in HIPAA mode), list and get leads, create a lead, list bookings and website chats, queue an outbound AI call, and add a number to the Do Not Call list. Each tool checks its own scope, so a key with only read scopes cannot queue calls. Two companion servers cover Vocenya developer docs and public site information, both read-only.
When to use it
Use it when an assistant should answer questions about a business's phone and chat activity, pull leads or appointments, push a lead in from another system, or request an AI callback. The docs and site servers suit questions about the Vocenya API and about Vocenya's plans and products.
Requirements
A remote Streamable HTTP endpoint; nothing to install. The platform server needs either OAuth sign-in by an account owner or an Authorization header with a Bearer API key (vk_live_ or vk_test_). Docs and site servers need no authentication. Rate limits apply: 60 requests a minute per IP for public servers, 120 a minute per key for the platform server.
Before you install
The platform server reads customer call transcripts, leads and chat messages, and can write: create_lead, queue_outbound_call and add_do_not_call change account data or cause real calls. Keep the Authorization key in an environment variable, never in a chat or commit. Test keys use sample data and never ring anyone. HIPAA-mode accounts return no transcripts, summaries or chat messages, and connecting an AI client does not extend a BAA to it.

Installation

In SourceWeft

  1. Open Vocenya in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "platform": {
      "type": "http",
      "url": "https://vocenya.com/mcp/platform"
    }
  }
}

README

Vocenya MCP servers

[License: MIT] [MCP Registry]

[Vocenya Site on AllMCPs] [Vocenya on AllMCPs] [Vocenya Docs on AllMCPs]

Connect Claude, ChatGPT, Cursor, VS Code and other AI assistants to Vocenya, the AI receptionist for small businesses made by GH Business Solutions, and to its developer docs.

Vocenya answers phone calls and website chats 24/7, books appointments, captures leads, hands calls to trained people and places outbound AI calls with Do Not Call, consent and calling-hours checks. It runs three remote Model Context Protocol servers over Streamable HTTP. Nothing to install: point your client at a URL.

Full guide: https://vocenya.com/docs/mcp

ServerURLAuthWhat it does
Vocenya Docshttps://vocenya.com/mcp/docsNoneSearch the Vocenya developer docs and get every REST endpoint with code samples. Read-only.
Vocenya (platform)https://vocenya.com/mcp/platformOAuth or API keyOne business account's calls, leads, bookings and chats; add leads, queue outbound AI calls, update the Do Not Call list.
Vocenya Sitehttps://vocenya.com/mcp/siteNoneAnswers about Vocenya itself from vocenya.com: plans and prices, products, industries, locations, guides. Read-only.

The public servers allow 60 requests a minute per IP address. The platform server shares the API key's REST limit (120 requests a minute per key by default).

This repository holds the official MCP Registry entries, a Claude Code plugin and these instructions. The servers are hosted by Vocenya; their code is not here.

Tools

Vocenya Docs (no key, read-only)

ToolWhat it does
search_docsSearch guides (authentication, webhooks, pagination, outbound calling rules, live chat, MCP) and every API endpoint.
get_doc_pageOne docs page as Markdown, for example quickstart, webhooks or reference/leads.
list_endpointsREST endpoints with method, path, summary and required scope, grouped by resource.
get_endpointOne endpoint in full: scope, parameters, request body, responses and code samples in cURL, Node, PHP and Python.

Vocenya platform (OAuth or API key)

ToolScopeWhat it does
list_callscalls:readCalls handled by the AI, GH Live agents or the team, newest first.
get_callcalls:readOne call with its leads; AI summary and transcript unless the account is in HIPAA mode.
list_leadsleads:readLeads from calls, chats and forms.
get_leadleads:readOne lead with contact details, reason, urgency and source.
create_leadleads:write (+ outbound:write for an AI callback)Add a lead from another system; optionally ask the AI to call back.
list_bookingsbookings:readAppointments the AI booked into the business calendar.
list_chatschats:readWebsite live chat conversations.
queue_outbound_calloutbound:writeAsk the AI to call someone who consented. Compliance is checked first; refusals return the reason.
add_do_not_calldnc:writeAdd a number to the business's Do Not Call list.

Each tool checks its own scope (the API key's, or the scopes an owner approved when connecting with OAuth), so a key with only leads:read can read leads but cannot queue calls. Test keys (vk_test_...) work on separate sample data and never ring anyone. Accounts in HIPAA mode never return transcripts, AI summaries or chat messages through MCP.

Vocenya Site (no key, read-only)

get_pricing, get_service, search_industries, get_industry, list_locations, search_articles, get_article, and the resource vocenya://llms.txt.

Authentication

  • Docs and Site: none.
  • Platform, OAuth (no key): clients that sign in with OAuth (Claude Code, Claude connectors, ChatGPT developer mode and others) just need the URL. The client registers itself, then an account owner signs in to Vocenya and chooses the account, live or test data, and the permissions (the same scopes as API keys). Owners see and disconnect connected apps on the Developers page: https://vocenya.com/app/developers. The server supports OAuth 2.1 authorization code with PKCE (S256) and dynamic client registration.
  • Platform, API key: Authorization: Bearer vk_live_... (or vk_test_... for test data). The account owner creates keys, each with its own scopes, on the same Developers page. Keep keys in environment variables; never paste them into a chat or commit them.

Connect

Claude Code

bash
# Docs (no key)claude mcp add --transport http vocenya-docs https://vocenya.com/mcp/docs
# Platform with OAuth (Claude Code opens the Vocenya sign-in)claude mcp add --transport http vocenya https://vocenya.com/mcp/platform
# Or platform with an API key in an environment variableclaude mcp add --transport http vocenya https://vocenya.com/mcp/platform \  --header "Authorization: Bearer $VOCENYA_API_KEY"

Or install the plugin from this repository, which adds the docs server and two skills (REST API and webhooks, website live chat install):

bash
claude plugin marketplace add gadyamedia/vocenya-mcpclaude plugin install vocenya@vocenya

Claude Desktop and claude.ai

Docs server: Settings > Connectors > Add custom connector, URL https://vocenya.com/mcp/docs, no authentication.

Platform server: add a custom connector with the URL https://vocenya.com/mcp/platform and sign in with your Vocenya owner account (OAuth).

Or, with an API key, through the mcp-remote bridge in claude_desktop_config.json:

json
{    "mcpServers": {        "vocenya": {            "command": "npx",            "args": [                "-y",                "mcp-remote",                "https://vocenya.com/mcp/platform",                "--header",                "Authorization:${VOCENYA_AUTH}"            ],            "env": {                "VOCENYA_AUTH": "Bearer paste-your-key-here"            }        }    }}

Cursor

~/.cursor/mcp.json:

json
{    "mcpServers": {        "vocenya-docs": { "url": "https://vocenya.com/mcp/docs" },        "vocenya": {            "url": "https://vocenya.com/mcp/platform",            "headers": { "Authorization": "Bearer ${env:VOCENYA_API_KEY}" }        }    }}

VS Code

.vscode/mcp.json (VS Code asks for the key once and stores it securely):

json
{    "inputs": [        {            "type": "promptString",            "id": "vocenya-key",            "description": "Vocenya API key (vk_live_... or vk_test_...)",            "password": true        }    ],    "servers": {        "vocenya-docs": {            "type": "http",            "url": "https://vocenya.com/mcp/docs"        },        "vocenya": {            "type": "http",            "url": "https://vocenya.com/mcp/platform",            "headers": { "Authorization": "Bearer ${input:vocenya-key}" }        }    }}

ChatGPT

Turn on developer mode, then add a custom connector with the URL https://vocenya.com/mcp/docs and no authentication. For your account data, add https://vocenya.com/mcp/platform with OAuth and sign in with your Vocenya owner account.

Any other client

Any client that supports Streamable HTTP works. For the platform server, sign in with OAuth, or send Authorization: Bearer <your key>.

Example prompts

  • "Using the Vocenya docs, how do I verify a webhook signature? Show Node code."
  • "Which scope do I need to create a lead, and what does the request body look like?"
  • "Show the leads my AI receptionist captured this week." (platform)
  • "What appointments did the AI book for next Monday?" (platform)
  • "How much does Vocenya cost and how many AI minutes does each plan include?" (site)

Official MCP Registry

The files in registry/ are the entries published to the official MCP Registry under the com.vocenya namespace (com.vocenya/docs, com.vocenya/platform, com.vocenya/site).

Links

Privacy

The docs and site servers are read-only and cannot see any customer account. The platform server sees only the one business account that owns the API key (or that an owner chose when connecting with OAuth), and only what the approved scopes allow. HIPAA mode is a paid add-on with a signed BAA; connecting an AI client does not make that client covered by the BAA, so only send patient data to AI tools you have your own agreements with. Full policy: https://vocenya.com/privacy

Support, security and license

  • Questions and corrections: open an issue, or email [email protected]
  • Security reports: see SECURITY.md
  • License: MIT for the contents of this repository. The Vocenya service itself is a hosted commercial product under the Vocenya terms.

Copyright (c) 2026 DRAKB LLC dba GH Business Solutions.

Source: README.md at commit 8d0aaaa

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.1.0LatestOct 5, 2026