# Vocenya [Verified owner] [Health: Active]

**Category:** 💬 Communication  
**Repository:** https://vocenya.com/mcp/platform  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/vocenya

## Description
Connect an AI assistant to one Vocenya business account: list calls, leads, bookings and chats, add leads, queue compliant AI callbacks and update Do Not Call.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: medium). Install path inferred — verify against the README before running it. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "vocenya": {
    "url": "https://vocenya.com/mcp/platform"
  }
}
```

## Documentation

## What Vocenya MCP server does

The Vocenya MCP server gives an AI assistant access to one Vocenya business account. Its scope covers common communication and customer-management records: calls, leads, bookings, and chats. The assistant can retrieve lists of these records rather than working across multiple Vocenya accounts through one connection.

The server also supports several account actions. An assistant can add leads, queue compliant AI callbacks, and update Do Not Call information. These capabilities make the server relevant to workflows where an AI assistant needs to inspect customer activity and then create or modify supported records in Vocenya.

## Tools and capabilities

The available capabilities described for the Vocenya MCP server are:

- Listing calls
- Listing leads
- Listing bookings
- Listing chats
- Adding leads
- Queueing compliant AI callbacks
- Updating Do Not Call information

Developers should confirm those details in Vocenya’s current platform documentation before implementing against the server.

The read-oriented capabilities are useful for asking an assistant to review activity already recorded in Vocenya. The write-oriented capabilities cover adding a lead, placing a callback into the supported AI callback queue, and changing Do Not Call status or information. The description does not state whether these operations require additional confirmation, which callback fields are accepted, or how compliance rules are enforced.

## Limitations and notes

The Vocenya MCP server is scoped to one business account per connection.

Those details cannot be inferred from the listed capabilities. In particular, the description does not establish whether the server runs over standard input/output, HTTP, or another transport, so client selection should follow Vocenya’s own setup instructions.

The phrase “compliant AI callbacks” identifies the callback capability but does not document the compliance controls, consent model, geographic restrictions, scheduling rules, or audit behavior. Teams handling outreach should verify those requirements with Vocenya before enabling callback workflows. Likewise, updating Do Not Call information should be tested against the account’s existing records and business process before being automated.

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

