> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dialbird.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Claude, ChatGPT and other AI assistants

> Use Dialbird from Claude, ChatGPT and other AI assistants through the Dialbird MCP server.

Connect an AI assistant to Dialbird and work with your calls, texts, contacts and campaigns in plain language. The assistant reaches Dialbird through our MCP (Model Context Protocol) server and only sees what you can see in the Dialbird app: the numbers assigned to you and the contacts shared with you.

**MCP server URL**

```text theme={null}
https://api-prod.dialbird.io/mcp
```

You'll also find this URL, with a copy button, in Dialbird under **Settings → Integrations → AI assistants**.

## Before you start

* A Dialbird account in a workspace whose plan includes integrations.
* At least one Dialbird number assigned to you.
* To send texts: a number that has finished business verification, and credits in your workspace.

## Connect

<Tabs>
  <Tab title="Claude">
    <Steps>
      <Step title="Add the connector">
        In Claude, open **Settings → Connectors**. Add **Dialbird** from the directory, or choose **Add custom connector** and enter `https://api-prod.dialbird.io/mcp`.
      </Step>

      <Step title="Sign in">
        Select **Connect** and sign in with your Dialbird account.
      </Step>

      <Step title="Choose what Claude can do">
        Review the permissions. **Also let Claude send text messages for you** is ticked by default; untick it for a read-only connection. Then select **Allow access**.
      </Step>
    </Steps>
  </Tab>

  <Tab title="ChatGPT">
    <Steps>
      <Step title="Add the connector">
        In ChatGPT, open **Settings → Apps & Connectors**. Add **Dialbird**, or create a custom connector with the URL `https://api-prod.dialbird.io/mcp` and OAuth authentication. Custom connectors depend on your ChatGPT plan.
      </Step>

      <Step title="Sign in and allow access">
        Sign in with your Dialbird account, choose whether ChatGPT may send texts, and select **Allow access**.
      </Step>
    </Steps>
  </Tab>

  <Tab title="Claude Code">
    Add the server, then run `/mcp` inside Claude Code to sign in:

    ```bash theme={null}
    claude mcp add --transport http dialbird https://api-prod.dialbird.io/mcp
    ```
  </Tab>

  <Tab title="Other MCP clients">
    Any client that supports remote MCP servers over Streamable HTTP with OAuth can connect to `https://api-prod.dialbird.io/mcp`; it registers itself and opens the Dialbird sign-in page.

    Developer tools that can't do OAuth can send a Dialbird API key instead, as `Authorization: Bearer <your API key>`. An API key acts as the teammate who created it.
  </Tab>
</Tabs>

## What the assistant can do

| Area | What you can ask for | Tools |
| - | - | - |
| Account | Who is signed in, and which numbers you can use | `whoami`, `list_numbers` |
| Calls | Recent calls with AI summaries, next steps, transcripts and voicemails | `list_calls`, `get_call` |
| Texts | Find unread or unanswered threads, read them, and reply | `list_conversations`, `get_conversation`, `send_message` |
| Contacts | Look up, create and update contacts; see your contact lists | `search_contacts`, `get_contact`, `create_contact`, `update_contact`, `list_contact_lists` |
| Campaigns | Create a campaign, load a list of people into it, or add existing contacts | `list_campaigns`, `get_campaign_contacts`, `create_campaign`, `import_contacts_to_campaign`, `add_contacts_to_campaign` |
| Broadcasts | Check the reach and cost of a broadcast, then send, schedule or cancel it | `estimate_broadcast`, `send_broadcast`, `cancel_broadcast` |

<Note>
  Tools that only read run straight away. In Claude and most other assistants, tools that create, change or send ask for your approval before they run.
</Note>

## Good to know

* **Texts cost credits.** Messages and broadcasts are billed to your workspace exactly like sending from the app.
* **Campaign broadcasts respect working hours.** Texts go out only inside the sending number's working hours, in each contact's own time zone, so a broadcast sent at the weekend may start on Monday. The assistant tells you when the first texts will go.
* **Opt-outs are always honoured.** Opted-out, blocked and do-not-call contacts are skipped.
* **Imports stay in the campaign.** People imported with `import_contacts_to_campaign` are added to that campaign only, not to your contacts.
* **Replies only.** `send_message` replies in an existing conversation; it doesn't text new numbers.

## Example prompts

* "What did customers call about this week? Group the calls by topic."
* "Which texts on my main number haven't been answered yet? Draft replies for me to check."
* "Add Jane Smith from Acme, +44 7700 900123, as a contact."
* "Create a campaign called October follow-ups on my sales number and add these 40 leads to it."
* "How much would it cost to text everyone in the Newsletter list about Friday's sale?"

## Manage connected assistants

In Dialbird, go to **Settings → Integrations** and open the **AI assistants** card. It shows:

* The MCP server URL, with a copy button, and a link to this guide.
* Every assistant connected to your account, such as Claude, ChatGPT or Cursor, with when it was connected and whether it can send text messages.

Each assistant you connect appears separately, so you can connect more than one and remove them one at a time. The card shows only your own connections; teammates manage theirs from their own settings.

## Disconnect

On the **AI assistants** card, select **Disconnect** next to the assistant and confirm. Its access ends within a few minutes, and it has to sign in again to reconnect.

You can also remove Dialbird from the assistant's own connector settings (in Claude, **Settings → Connectors**). Disconnecting in Dialbird is the way to be sure, for example if you no longer use that assistant or have lost access to it.

To change whether an assistant can send texts, disconnect it and connect again, ticking or unticking **Also let … send text messages**.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Authorization fails after signing in">
    Your workspace's plan may not include integrations, or your account may be suspended. Check your plan in Dialbird, or contact [support@dialbird.io](mailto:support@dialbird.io).
  </Accordion>

  <Accordion title="The assistant says it needs a permission to send">
    You connected without **Also let … send text messages**. Disconnect the assistant on the **AI assistants** card in **Settings → Integrations**, connect again, and leave the box ticked.
  </Accordion>

  <Accordion title="A broadcast was accepted but nothing was sent yet">
    Campaign texts wait for the sending number's working hours. Change the number's working hours in Dialbird to send outside them.
  </Accordion>
</AccordionGroup>

Need help? Email [support@dialbird.io](mailto:support@dialbird.io).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.