Start here
Operate your Dapta workspace from Claude, ChatGPT, Codex, Cursor or your own scripts, using plain language. Sign in with your Dapta account or connect with an API key.
The Dapta MCP lets you operate your Dapta workspace from inside an AI client such as claude.ai, Claude Desktop, Claude Code, ChatGPT, Codex or Cursor, using plain language. Instead of clicking through the dashboard, you ask Claude to "create a voice agent", "show me last week's connection rate" or "add a step to this flow", and it does it for you.
It is built on the Model Context Protocol (MCP), an open standard for connecting AI assistants to external systems. The server gives Claude tools: the actions it can take, such as reading data, creating agents, updating prompts, patching flows or writing rows. Each tool comes with a title and a description of what it does and when it is used, so Claude can pick the right ones for your request.
What you can do
Voice agents
Create, configure and calibrate agents. Improve prompts from real calls
Voice analytics
Call stats, connection rates, best hours to dial, qualified leads, feedback
Voice sequences
Read and adjust outbound calling lists, contacts and retry rules
Text and WhatsApp agents
Build chat agents, test them, manage versions, connect a WhatsApp line
Flow Studio
Design, validate, create, patch and run automation flows. Read execution logs
Dapta databases
Create databases and tables, read and write the rows automations keep
CRM
Find contacts and trace what happened to each one. Create and edit contacts, leave notes, add them to lists, move them through pipeline stages
Sales meetings
Meeting transcripts, action items and statistics
Workspace and account
Phone numbers, knowledge bases, WhatsApp templates, balance, subscription
Support and docs
Search Dapta's documentation. FAQ and navigation help
You do not need to know any tool names. You describe what you want, and Claude picks the right actions.
Two ways to connect
Sign in with your Dapta account. Recommended for people. Your AI client opens Dapta's sign-in page once and stays connected. There is no key to copy, and one connection reaches every workspace you can use. Works in claude.ai, Claude Desktop, Claude Code, ChatGPT, Codex and Cursor.
API key. For scripts, automations, or a connection fixed to one workspace. The workspace owner creates keys in the Dapta admin panel.
Safe by design
Workspace isolation. Every call runs in one workspace: the one tied to your API key, or the one you chose after signing in.
Preview, then confirm. Whenever Claude changes something, it shows you a preview first and waits for your yes. Reading your data does not need confirmation.
Keys stay on the server. Your Dapta API key and your login session are never returned to Claude.
Flow credentials are redacted. Tokens and API keys saved inside your flow steps come back to Claude as
«redacted». Claude can still keep them or replace them when it edits a flow.
Who this is for
Anyone with a Dapta account who is an owner or admin of at least one workspace. Signing in needs nothing else and reaches each of those workspaces. API keys are created by the workspace owner.
Key ConceptsLast updated