📟Connect Codex

Connect the Dapta MCP to the Codex CLI. Add one block to your Codex config file, restart, and Codex can drive your Dapta workspace.

Codex reads its MCP servers from a config file on your machine. You add one small block with your key, restart Codex, and it can call Dapta directly. There is nothing else to install.

You will need the API key from the previous step. If you do not have one yet, see Mint your API key.

---

Step 1: Create your API key. It appears once in a dialog titled Save your new MCP key. From that dialog you can copy the ready-made Codex block, or copy the key and build the block yourself. The key cannot be shown again later, so keep it somewhere safe.

---

Step 2: Open the file ~/.codex/config.toml and add the block below. Replace <your-key> with the key you copied.

~/.codex/config.toml

[mcp_servers.dapta-ai]
url = "https://mcp.dapta.ai/mcp"
http_headers = { "x-api-key" = "<your-key>" }

If the file does not exist yet, create it. If you already have other [mcp_servers.*] entries, add this block alongside them.

---

Step 3: Restart Codex so it picks up the new server. Then ask it something about your Dapta workspace, for example: "Create a voice agent in Dapta". Codex receives Dapta's workflow guidance automatically over the connection, so there is no extra install step.

---

What you can ask for

Once connected, you can ask across your Dapta workspace:

• 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.

Your data stays safe. Your key is scoped to one workspace, so Codex only ever sees that workspace and cannot reach any other. When it changes something (an agent, a prompt, a flow, or a ticket), it shows you a preview first and waits for your confirmation before applying. Reading information never needs confirmation.