MCP server
DURUM.ai exposes an MCP server (Model Context Protocol) to connect an AI assistant, such as Claude or ChatGPT, directly to your data: ad spend, attribution, funnel, contacts, calls and ad rules.
Paid tier required
The MCP server is reserved for paid tiers (Starter, Growth, Scale). On the Discovery plan, the connection is refused at the consent screen and every call returns 403 plan_free_no_api. To upgrade: Settings, Billing, Upgrade.
Connect
- In your MCP client, add a remote server with the address
https://app.durum.ai/mcp. - The client opens a DURUM.ai consent page: sign in, choose the account (business) and the access granted, then approve.
- Only the account owner and its administrators can approve a connection.
Access follows the same rules as API keys: the approved scopes limit what the assistant can read or change, and every call is logged.
Connect with an API key (platforms without OAuth)
Some agent platforms only take an address and headers, with no consent page. In that case:
- In DURUM.ai, Settings, API keys: create a key with the scopes you want (for example
read:dashboard,read:ads,read:calls). It is shown only once. - In the platform, address
https://app.durum.ai/mcp, then one header:
| Header | Value |
|---|---|
Authorization | Bearer durum_sk_live_... |
The key sets the account and the scopes: the assistant only sees the tools of those scopes. An organization key adds the list_accounts tool and requires client_key on every call. A revoked or expired key returns 401.
Common errors
| Code | Cause |
|---|---|
plan_free_no_api | the workspace is on the Discovery plan |
insufficient_scope | the approved access does not cover this tool |
forbidden | the resource does not belong to the connected account |