Connect from the Claude connectors directory

Connect Dapta to Claude from the Claude connectors directory: requirements, how to sign in, how to choose a workspace, three prompts to start with, and how your data is protected.

Dapta is the official Dapta connector for Claude. It lets you operate your Dapta workspace in plain language: voice agents, text and WhatsApp agents, automations, call analytics and more.

What you can do

Area

Examples

Voice agents and analytics

Create and configure agents. Call stats, connection rates, best hours to dial, qualified leads

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

Sales meetings

Meeting transcripts, action items and statistics

Workspace and account

Phone numbers, knowledge bases, WhatsApp templates, balance, subscription

Documentation

Search Dapta's documentation from the chat

Requirements

A Dapta account with access to at least one workspace. The connector works on your own Dapta data, so without an account there is nothing to see.

Connect

From the directory

In Claude, open Connectors.
Find Dapta and click Connect.
Sign in with your Dapta account.
Approve the access.

As a custom connector

In claude.ai or Claude Desktop go to Settings, then Connectors, then Add custom connector.
Paste the server URL:
```
https://mcp.dapta.ai/mcp
```
Name it Dapta and click Add. Leave the OAuth client fields empty. Claude sends you to Dapta's login page. Sign in and approve.

In Claude Code

terminal

claude mcp add --transport http dapta https://mcp.dapta.ai/mcp

Then run /mcp inside Claude Code and choose Authenticate next to dapta.

Choose your workspace

If your account has one workspace, Claude uses it. If it has several, Claude lists them by name and asks which one to work in. Answer with the name.

Say "Switch to <name>" to change workspace at any time.
Every answer starts with the workspace it ran in, so you always know where you are.

Three prompts to start with

Prompt

What Claude does

"Who am I in Dapta, and which workspaces can I use?"

Confirms your connection and lists your workspaces, using whoami and list_my_workspaces

"List my voice agents and show me how the newest one is configured."

Reads your agents and opens the most recent one, using list_agents and get_agent

"Show me the recent runs of my most recently updated flow, and tell me if any of them failed."

Finds your latest automation and reads its recent runs, using get_workspace_flows and get_flow_execution_logs

All three only read data. Nothing in your workspace changes.

What Claude can change, and how you are protected

Updates, deletions, publishing and flow runs are shown to you as a preview first, and nothing is applied until you confirm. Each tool declares whether it only reads, adds data, or changes and removes existing data, so Claude knows when to ask before acting. Your Dapta API key, your login session and your agents' secret keys are never returned to Claude.

Safety & Security

When to use an API key instead

Signing in is the best option for people. Use an API key for:

Automations: custom scripts and scheduled jobs.
Clients that cannot run a login: Cursor, Codex.
A fixed workspace: a key always works in the one workspace it was created for.

Mint your API key