Skip to Content
MCP Server (Preview)Getting Started

Getting Started

There are two ways to connect, and most people should use the first.

Sign in (recommended)API key
HowPaste the URL into your assistant and sign in to Dialora when it prompts youCreate a key in the dashboard and paste it as a header
Works withClients that support OAuth — Claude, ChatGPT, CursorAny MCP client
PermissionsYou approve them on a consent screen, per accountYou pick scopes when creating the key
Nothing to copy❌ — the key is a secret you must store safely

Remember the rate limits while the MCP server is in preview — 10 read tool calls every 30 seconds, 3 write tool calls every 90 seconds, and 20 requests every 5 seconds.

Add https://api.dialora.ai/mcp as a remote MCP server in your assistant. The first time it connects, your browser opens a Dialora sign-in page, then a consent screen.

On the consent screen you:

  1. See which app is asking (its name and the host it will return you to)
  2. Pick which account it may act on, if you have more than one
  3. Choose the permissions to grant, grouped by resource — Calls, Users, Plans, Subscriptions — each with a read level and a write level

Read permissions are ticked by default; write permissions are not. There are Read and Write shortcuts if you’d rather grant a whole tier at once.

Approve, and the assistant is connected. You never copy a secret, and you can deny at any point to cancel.

Dialora registers your assistant automatically the first time it connects, using the standard OAuth discovery your client already speaks. There is nothing to set up in the dashboard beforehand.

Option B: Use an API key

Use this for clients that don’t support OAuth, or for headless setups.

  1. Sign in to your Dialora dashboard.
  2. Open the profile avatar in the top right → API Keys.
  3. Create a new key and select the scopes you want the assistant to have.
  4. Copy the key — it looks like dlr_live_xxxxxxxxxxxxxxxx. You will only see it once.

Treat your API key like a password. Anyone with it can act on your Dialora account within the granted scopes.

Which scopes do I need?

A scope decides what a tool can do, and your key only exposes the tools its scopes allow. Grant the minimum the assistant needs:

If you want the assistant to…Grant scopeKey type
Read call history & transcriptscalls:readAccount or agency
Place outbound callscalls:writeAccount or agency
Manage end usersusers:read / users:writeAgency (tenant) key
Manage plans & subscriptionsplans:read, subscriptions:read / :writeAgency (tenant) key

Regular keys created from the profile avatar → API Keys can only grant calls:read and calls:write; the users, plans, and subscriptions scopes are reserved for agency (tenant) keys. See Authentication & Scopes for the full list.

Connect your assistant

All clients point to the same endpoint — https://api.dialora.ai/mcp. With an API key, add the header Authorization: Bearer dlr_live_…; with sign-in, your client handles the token for you. Pick your client below:

Option A — custom connector (recommended). Open Settings → Connectors → Add custom connector, paste https://api.dialora.ai/mcp, and set the OAuth client to No client ID — register one automatically. Dialora does not support Anthropic's hosted client metadata, so the option marked “Recommended” there fails to register. Sign in when the browser opens and approve the permissions — no API key, no Node.js.

Option B — config file. Use this to authenticate with a dlr_live_… key. Open Settings → Developer → Edit Config, add Dialora under mcpServers, then fully quit and reopen Claude Desktop. The config file only launches stdio servers, so it reaches Dialora through the mcp-remote bridge (needs Node 18+) and differs per OS:

{ "mcpServers": { "dialora": { "command": "npx", "args": [ "-y", "mcp-remote", "https://api.dialora.ai/mcp", "--transport", "http-only", "--header", "Authorization:${DIALORA_AUTH}" ], "env": { "DIALORA_AUTH": "Bearer dlr_live_xxxxxxxxxxxxxxxx", "PATH": "/opt/homebrew/bin:/usr/local/bin:/usr/bin:/bin" } } } }

Keep the env block: the PATH entry is what stops spawn npx ENOENT, and putting Bearer in DIALORA_AUTH (with no space after Authorization:) is what stops the header being split. Full walkthrough and per-OS fixes in Connect Claude.

For step-by-step details per client, see Connect Claude, Connect ChatGPT, or Connect Cursor. Using VS Code, Windsurf, Cline, Zed, LM Studio or anything else? See Connect Other Clients.

Try it

Ask your assistant something like:

“List my last 10 Dialora calls.”

or

“Place a call from +15551230001 to +15559876543 using agent agent_ck9z3.”

The assistant will call the matching Dialora tool and return the result. Actions that place real phone calls (create_call) are marked as side-effecting, so most clients will ask you to confirm first.

Endpoint summary

URLhttps://api.dialora.ai/mcp
TransportStreamable HTTP
AuthOAuth sign-in, or Authorization: Bearer dlr_live_…
Rate limits20 requests / 5s · reads 10 / 30s · writes 3 / 90s