> ## Documentation Index
> Fetch the complete documentation index at: https://developers.cloudtalk.io/llms.txt
> Use this file to discover all available pages before exploring further.
# CloudTalk MCP
> The CloudTalk MCP server connects Claude, Cursor, and other AI assistants to your CloudTalk account: search calls, read transcripts, manage contacts, send SMS, and run AI Voice Agents in natural language.
## What is MCP?
Model Context Protocol (MCP) is an open standard that lets AI assistants connect securely to business tools. Instead of copying data into a chat, you connect CloudTalk once. From then on, the assistant sees a set of CloudTalk tools (search calls, read a transcript, update a contact) and picks the right one for whatever you ask. Every request is authenticated with your API key and scoped to your account, and CloudTalk returns only the data that one tool call asked for.
## What you can do
Create and tune voice agents, manage their knowledge bases, and review how their calls went.
Search call history, pull transcripts, read AI summaries, sentiment, topics and smart notes.
A 360° view of any contact: every call, note and activity in one timeline.
Create and update contacts, tag calls and contacts, send SMS, place calls. Risky actions ask for confirmation first.
## Profiles
Assistants pick tools more reliably from a short, focused list. Connect the profile that matches the job instead of the full catalogue:
| Profile | URL | Built for | Start with |
| -------------- | --------------------------------------- | ------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------- |
| Voice agents | `https://mcp.cloudtalk.io/voice-agents` | Building and reviewing AI Voice Agents | [`create_voice_agent`](/guides/mcp/tools#cloudtalk_create_voice_agent) |
| Analytics | `https://mcp.cloudtalk.io/analytics` | Call analysis, QA, coaching, reporting, read-only | [`search_calls`](/guides/mcp/tools#cloudtalk_search_calls) |
| Contacts | `https://mcp.cloudtalk.io/contacts` | Managing contact data | [`get_contact_interactions_summary`](/guides/mcp/tools#cloudtalk_get_contact_interactions_summary) |
| Agent assist | `https://mcp.cloudtalk.io/agent-assist` | Reps on live calls: know the caller, act, log it | [`get_contact_interactions_summary`](/guides/mcp/tools#cloudtalk_get_contact_interactions_summary) |
| Campaigns | `https://mcp.cloudtalk.io/campaigns` | Outbound campaign operations, requires the new Sales Dialer add-on | [`launch_campaign_from_source`](/guides/mcp/tools#cloudtalk_launch_campaign_from_source) |
| Full catalogue | `https://mcp.cloudtalk.io` | Everything your account can access | |
## Common use cases
See the [Recipes](/guides/mcp/recipes) page for ready-to-use prompt chains, grouped by job: coaching and QA, live-call assist, AI Voice Agents, and contact data.
## Actions ask for confirmation
Many tools that send, dial, or change data return a preview of exactly what would happen instead of acting, and execute only when the call carries explicit confirmation. Each one is marked **Asks for confirmation** in the [tool reference](/guides/mcp/tools). **The assistant is what decides to show you the preview and ask** — CloudTalk keeps no record that one was returned, so this is a review step your assistant honours rather than a lock CloudTalk enforces. Choose an assistant and a client whose approval prompts you trust. Nothing in the catalogue can delete contacts, calls or recordings.
## Security
* Every tool is scoped to your company by the API key. No tool accepts an account ID, so an assistant can't reach another company's data.
* CloudTalk sees only tool parameters (a date range, a call ID), never your conversation with the assistant.
* Recording links are signed and expire within 12 hours, often sooner, and every access is logged in CloudTalk's audit trail.
* Revoke the API key in the Dashboard to cut off access; revocation can take a few minutes to take effect.
## Availability
MCP is available on the **Essential plan and higher**. Two areas depend on what else is on your plan:
* **AI insights** (summaries, sentiment, topics and transcripts) require Conversation Intelligence. Calls without it return empty AI fields rather than an error.
* **Campaign tools** require the new **Sales Dialer** add-on.
## Limits and freshness
* **60 requests per minute per company.** A `429` means wait a minute and retry.
* Reads are cached briefly (seconds to minutes) to keep responses fast; 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.
* AI insights need a recorded, processed call. A call that hasn't been analysed yet returns empty AI fields, which is a normal answer.
## FAQ
MCP is available on the **Essential plan and higher**. AI insights (summaries, sentiment, topics, transcripts) additionally require Conversation Intelligence, and the campaign tools require the new Sales Dialer add-on. If you're on Starter, [upgrade your plan](https://www.cloudtalk.io/pricing/) to get access.
CloudTalk MCP authenticates with an API key in a request header, so what decides it is whether your client can send one. **Clients you configure yourself** send it from your own machine and work today: Claude Code, Cursor, and any client that supports Streamable HTTP with a custom header. **Hosted connectors** — Claude.ai, Claude Desktop, Claude mobile, ChatGPT — connect from the provider's cloud and need either a request-header field or OAuth sign-in. Not every Claude organization has a request-header field; ChatGPT offers OAuth sign-in only, and CloudTalk does not support OAuth yet, so an OAuth-only connector cannot connect. The [Quickstart](/guides/mcp/quickstart) has the setup, and the failure to expect, for each.
It can't delete a contact, call or recording. It can still remove data through a write: updating a contact or replacing a campaign's sources replaces the tags, numbers or emails you don't include, removing call tags detaches them, and deleting a campaign is terminal: `archived` is the reversible option, `deleted` cannot be undone. The actions that carry the most weight ask for confirmation first, marked in the [tool reference](/guides/mcp/tools).
Only the tool calls: a date range, a call ID. Your conversation stays with your AI provider; whether the assistant stores or trains on your chats is governed by that provider's settings, not CloudTalk's.
One API key is scoped to one company, so two accounts means two keys. In clients you configure yourself — Claude Code, Cursor — register one server per account. In a Claude connector the request header is stored for the whole organization, so everyone using that connector acts as the single account whose key it holds.
## Next steps
Connect Claude, Cursor, or another MCP client in five minutes.
Every tool with its parameters, defaults and limits.
## Related topics
- [CloudTalk MCP Tool Reference](/guides/mcp/tools.md)
- [Quickstart: Connect Your AI Assistant to CloudTalk](/guides/mcp/quickstart.md)
- [Changelog](/changelog.md)