# MCP Server

URL: https://docs.didlogic.com/docs/guides/apps-developer-tools/mcp-server

The didlogic MCP server connects AI assistants such as Claude, ChatGPT and Cursor to your didlogic account through the [Model Context Protocol](https://modelcontextprotocol.io).

**Server URL:** `https://mcp.didlogic.com/mcp`

info

Available on the Plus plan. Contact your account manager for temporary access.

## Why use it

- **No integration code.** Ask in plain language, and the assistant calls the didlogic API for you.
- **Full API coverage.** The server supports every operation of the public API v1 and v2: numbers, SIP accounts, routing, SMS, Click2Call, call history, recordings, reports, HLR lookups, compliance documents and billing.
- **Multi-step tasks in one request.** For example, the assistant can find a number, buy it, create a SIP account and route the number to it.
- **Analysis on top of your data.** The assistant can pull call history or reports and then summarize, compare or flag anything unusual.

## How it works

1. You connect the server to your assistant and sign in to didlogic.
2. When you ask for something, the assistant finds the API operation it needs (`search`), reads its arguments (`get_schema`) and runs it (`execute`).
3. Every call is made on behalf of your account, so the assistant can do exactly what your account can, no more.

See the [OpenAPI specification](https://docs.didlogic.com/docs/openapi-spec) for every operation and argument.

## Connect your assistant

Sign-in with OAuth is the recommended way to connect: you log in to didlogic in a pop-up window, and you don't need to copy any keys. If your assistant doesn't support OAuth, use an [API key](#connect-with-an-api-key) instead.

When you sign in, we create an API key named **Didlogic MCP auth key** in [API & Webhooks](https://app.didlogic.com/app/api-webhooks). Each new sign-in creates a separate key.

### Claude (desktop and web)

1. Open **Settings** → **Connectors** and click **Add custom connector**.

2. Enter:

   - **Name:** `didlogic`
   - **Remote MCP server URL:** `https://mcp.didlogic.com/mcp`

3. Click **Add**, then **Connect**, and sign in to didlogic in the pop-up window.

### ChatGPT

1. Open **Settings** → **Plugins** → **MCPs** and click **Add MCP server**. You can also go to **Plugins** → **Add** → **Add custom MCP server**.

2. Enter:

   - **Name:** `didlogic`
   - **MCP server URL:** `https://mcp.didlogic.com/mcp`
   - **Authentication:** `OAuth`. Leave **Client ID** and **Client secret** empty.

3. Save the server and sign in to didlogic in the pop-up window.

### Claude Code

Run:

```bash
claude mcp add --transport http didlogic https://mcp.didlogic.com/mcp
```

Then run `/mcp` in Claude Code, select **didlogic** and sign in.

### Cursor and other clients

Add the server to your MCP configuration file:

```json
{
  "mcpServers": {
    "didlogic": {
      "url": "https://mcp.didlogic.com/mcp"
    }
  }
}
```

The client opens the didlogic sign-in window the first time it connects.

### VS Code

Add the server to `.vscode/mcp.json`:

```json
{
  "servers": {
    "didlogic": {
      "type": "http",
      "url": "https://mcp.didlogic.com/mcp"
    }
  }
}
```

### Set it up with an AI agent

If you're configuring the connection with a coding agent, point it to [mcp.didlogic.com/llms.txt](https://mcp.didlogic.com/llms.txt). The file has setup instructions for every client.

## Connect with an API key

Use an API key if your assistant doesn't support OAuth. First, create a key at [API & Webhooks](https://app.didlogic.com/app/api-webhooks).

warning

The key gives full access to your account. Don't share it or paste it into chats.

### Claude Desktop extension

1. Download [didlogic.mcpb](https://mcp.didlogic.com/didlogic.mcpb).
2. Open the file and click **Install**. A "not verified" warning is expected.
3. Paste your API key.
4. Check that **Settings** → **Extensions** → **didlogic** is turned on.

### Other clients

Add the key as an `Authorization` header:

```json
{
  "mcpServers": {
    "didlogic": {
      "url": "https://mcp.didlogic.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}
```

## What you can ask

Once connected, just ask. You don't need any special keyword, but mentioning didlogic helps the assistant pick the right tool when you have several connectors.

### Launch a number in a new country

> Buy a mobile number in Germany, create a SIP account called "Support DE" and route the number to it.

The assistant checks which documents the German numbers require and whether your documents are already verified, then buys the number, creates the SIP account and sets up the route. If a document is missing, it tells you what to upload.

### Get a weekly traffic report

> Show my outbound calls for the last 7 days by destination: number of calls, minutes, spend and ASR. Highlight destinations where ASR dropped compared to the week before.

The assistant pulls your call statistics and ASR report and puts them in a table. A sudden ASR drop on one destination is often the first sign of a routing problem.

### Spot suspicious traffic

> Did any SIP account make calls to unusual or expensive destinations in the last 24 hours? Compare with my usual traffic.

The assistant checks recent calls against your normal pattern and flags anything unusual, such as calls at night, new countries or premium-rate numbers. You can then ask it to change the SIP account password or tighten its IP restrictions.

### Clean a call list before a campaign

> Run an HLR lookup on these 200 numbers and give me back only the active mobile numbers, with their current carrier.

The assistant runs the lookups and returns a cleaned list, so your campaign doesn't waste calls on disconnected numbers. Each lookup is charged.

### Check a price before calling

> How much would a 10-minute call to a mobile number in the Philippines cost from my account?

The assistant quotes the price at your account's rates.

### Find and download call recordings

> Find yesterday's calls to +44 20 7946 0000 longer than 2 minutes and download the recordings.

### Audit your setup

> List all my numbers that have no destinations, and all SIP accounts that haven't made a call in the last 30 days.

The assistant finds numbers whose calls go nowhere and SIP accounts you may no longer need.

### Bulk changes

> Set the caller ID of all SIP accounts with "Sales" in the name to +1 415 555 0100.

One request instead of editing every account by hand.

### Call and message

> Call +1 212 555 0123 from my SIP account 12345 using Click2Call.

> Send an SMS from my US number to +1 212 555 0123: "Your appointment is confirmed for tomorrow at 10 AM."

## Stay in control

The assistant can run any operation your account allows, including purchases and deletions. The server marks these operations as changing data or charging money, and most assistants ask for your approval before running them. Read what the assistant is about to do before you approve, and avoid auto-approving actions in your assistant's settings.

warning

AI assistants can misread instructions. Always check changes to numbers, routing and SIP accounts, and any purchase made through an assistant. You're responsible for actions taken in your account.

To disconnect the assistant, delete its key at [API & Webhooks](https://app.didlogic.com/app/api-webhooks): **Didlogic MCP auth key** for OAuth, or the key you created yourself. The assistant loses access immediately. Then remove the didlogic connector in the assistant's settings.

## Billing

The MCP server itself is free. Actions you take through it are billed the same way as in the portal or API: number purchases, calls, SMS and HLR lookups.

## Troubleshooting

- **The assistant doesn't use didlogic.** Check that the connector is turned on for the current chat, and mention didlogic in your request.
- **Sign-in window doesn't open.** Allow pop-ups for your assistant, or connect with an [API key](#connect-with-an-api-key).
- **"Not an operation you can call" or "not permitted for your account".** The assistant can only do what your account can. Contact your account manager to enable a feature.
- **"Sign in again".** The key was deleted or is no longer valid. Reconnect the assistant.
- **Large requests run slowly or stop partway.** The server makes up to 1 API call per second, and up to 50 calls per step. For large jobs, such as HLR lookups on thousands of numbers, ask the assistant to work in batches.