CloudTalk MCP Server: Connect Claude, Cursor and Your Own AI Agents

The CloudTalk MCP server is CloudTalk’s own MCP implementation, hosted at mcp.cloudtalk.io. It exposes 49 tools across six areas: calls and analytics, contacts, messaging and calling, AI Voice Agents, campaigns, and connection and account lookups. Connect it to Claude, Cursor or an agent you built yourself, and that assistant can search your call history, read transcripts, manage contacts, send SMS and run AI Voice Agents using your real account data.

Nothing beyond your plan. MCP is included from the Essential plan up, which starts at $29 per user per month billed annually. Two areas depend on what else you have: AI insights, meaning summaries, sentiment, topics and transcripts, require Conversation Intelligence, and the campaign tools require the Sales Dialer add-on. Voice Agent tools work on your free AI Voice Agent minutes with no add-on. See full pricing for the plan breakdown.

Essential or higher. MCP is not available on Starter. If you are on Starter today, moving to Essential is what turns it on. Calls that have not been analysed return empty AI fields rather than an error, so a missing Conversation Intelligence add-on shows up as a blank summary, not a broken connection.

There is no switch to flip in the product. You connect a client to the server in four steps:

1. Generate an API key. In the CloudTalk Dashboard, create an API Access Key ID and Secret. You need admin access.
2. Encode the credentials. Base64 encode the ID and Secret and send them as an Authorization: Basic header.
3. Point your client at the server. Use mcp.cloudtalk.io for everything, or a profile URL such as mcp.cloudtalk.io/analytics for a shorter tool list.
4. Check the connection. Run cloudtalk_health_check. If the key resolves, you are connected.

The developer quickstart has the exact config for each client, plus the failure to expect from each one.

Anything the 49 tools cover, phrased the way you would say it to a colleague. Four jobs it handles well:

• Coaching and QA: find the calls where a deal stalled, read the transcripts, and summarise what the rep missed.
• Live call assist: pull one contact’s full history before you dial, then log the outcome without leaving the assistant.
• Voice agent work: create an AI Voice Agent, attach a knowledge base, and check how its calls went.
• Contact data: find duplicate or stale records, update them, and tag them in bulk.

Clients you configure yourself work today: Claude Code, Cursor, and any client that supports Streamable HTTP with a custom header. These send the API key from your own machine, so nothing has to be enabled for you first.

Hosted connectors are different. Claude.ai, Claude Desktop and Claude mobile connect from Anthropic’s cloud and need a request-header field, which Anthropic enables per organization, so whether it appears depends on your Claude organization rather than on CloudTalk. ChatGPT offers OAuth sign-in only and CloudTalk does not support OAuth yet, so ChatGPT cannot connect for now. OAuth support is planned.

Four controls carry the weight. Every tool is scoped to your company by the API key, and no tool accepts an account ID, so an assistant cannot reach another company’s data. CloudTalk sees only tool parameters, such as a date range or a call ID, never your conversation with the assistant. Recording links are signed, expire within 12 hours and often sooner, and every access is logged in CloudTalk’s audit trail. Revoking the API key in your Dashboard cuts off access, which can take a few minutes to take effect.

It cannot delete a contact, a call or a recording. It can still remove data through a write, which is worth knowing: updating a contact or replacing a campaign’s sources replaces the tags, numbers or emails you do not include, and removing call tags detaches them. Deleting a campaign is the one terminal action, and archiving is the reversible option. The actions that carry the most weight return a preview and ask for confirmation before they run.

Use MCP when a person or an agent is deciding what to do next, and the API when the steps are known in advance. MCP hands an assistant a catalogue and lets it choose, which is what you want for investigation, coaching, one-off analysis and agent work. A scheduled nightly sync into your warehouse has no decisions in it, so the API is the simpler fit. Most teams end up running both.

60 requests per minute per company. A 429 response means wait a minute and retry. Reads are cached briefly, seconds to minutes, to keep responses fast, and live queue stats are never cached. Records you change through the assistant update immediately, though a newly created voice agent or knowledge base can take a short while to appear in list results.

Developers, technical admins and partners running their own AI assistant against CloudTalk data. Setup involves an API key, a base64 encoding step and a config file, so one technical person on your side makes the difference between twenty minutes and an afternoon. Once it is connected, anyone on the team who uses that assistant gets the benefit without touching the setup again.