> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/dapta-mcp/mcp.md).

# Dapta MCP: Overview

The **Dapta MCP** lets you run your Dapta workspace by chatting with **Claude**. Instead of clicking through the dashboard, you ask Claude to "create a voice agent," "show me last week's connection rate," or "find my qualified leads," and it does it for you.

Setup is simple: you connect once with an API key, and Claude already knows the Dapta workflows. There is nothing extra to install beyond connecting. Your key is tied to one workspace, so Claude only ever sees and works with that workspace's data, and you never have to tell it which workspace to use.

{% hint style="info" %}
This is the same intelligence that powers **Dapti**, our in-app assistant. The difference is where it runs: the MCP brings Dapta into the Claude client you already use, instead of the chat inside `app.dapta.ai`.
{% endhint %}

***

## What you can do

Ask Claude to:

* **Voice agents:** create, configure, and calibrate voice agents, then review their call performance.
* **Text and WhatsApp agents:** build text agents and connect them to WhatsApp.
* **FlowStudio automations:** design and validate automation flows that wire your agents together.
* **Call and lead analytics:** pull call statistics, connection rates, recent calls, and lead intelligence.
* **Sales-meeting insights:** analyze recorded sales meetings for summaries and next steps.
* **Identity and billing:** check accounts, usage, balance, and subscription details.
* **Research and docs:** research a company from its website and search Dapta's documentation.

You do not need to know any tool names. You describe what you want in plain language, and Claude picks the right actions for you.

***

## Safe by design

* **Workspace isolation:** your key is scoped to a single workspace, so Claude cannot reach any other workspace or account.
* **Preview then confirm:** whenever Claude changes something (an agent, a prompt, a flow, a ticket), it shows you a preview first and waits for your confirmation before applying it. Reading your data does not need confirmation.
* **Key hygiene:** your key is shown only once and cannot be recovered later. There is one active key per workspace. To rotate it, revoke the old one and create a new one.

***

## Who this is for

Anyone with access to a Dapta workspace who wants to work faster from Claude. Creating an API key requires workspace-owner access. If you are not an owner, ask your workspace owner for a key, then follow the setup steps below.

***

## Get started

Two short steps: create your key and connect your Claude client, then start chatting.

{% content-ref url="/pages/mgrNs2Jy4B82jjw2FyzU" %}
[Setup & Connection](/dapta-mcp/setup.md)
{% endcontent-ref %}

{% content-ref url="/pages/LRJbKEAV5HB4G9Q0Ww1G" %}
[Key Concepts](/dapta-mcp/key-concepts.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.dapta.ai/dapta-mcp/mcp.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.