Getting Started
Connecting takes three steps: create an API key, add the MCP server to your assistant, and start asking.
Remember the rate limits while the MCP server is in preview β 1 tool call every 15 seconds per API key, and 20 requests every 5 seconds β so ask your assistant for one action at a time.
1. Create a Dialora API key
- Sign in to your Dialora dashboard.
- Go to Settings β API Keys.
- Create a new key and select the scopes you want the assistant to have (for example
calls:readandcalls:write). - 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 scope | Key type |
|---|---|---|
| Read call history & transcripts | calls:read | Account or agency |
| Place outbound calls | calls:write | Account or agency |
| Manage end users | users:read / users:write | Agency (tenant) key |
| Manage plans & subscriptions | plans:read, subscriptions:read / :write | Agency (tenant) key |
Regular keys created from Settings β API Keys can only grant calls:read / calls:write; the users, plans, and subscriptions scopes are reserved for agency (tenant) keys. See Authentication & Scopes for the full list.
2. Connect your assistant
All clients point to the same endpoint β https://api.dialora.ai/mcp β with the header Authorization: Bearer dlr_live_β¦. Pick your client below:
Open Settings β Developer β Edit Config and add Dialora under mcpServers, then fully quit and reopen Claude Desktop. Claude Desktop only launches stdio servers, so it reaches Dialora through the mcp-remote bridge (needs Node 18+). The config 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.
3. 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
| URL | https://api.dialora.ai/mcp |
| Transport | Streamable HTTP |
| Auth header | Authorization: Bearer dlr_live_β¦ |
| Rate limits | 20 requests / 5s Β· 1 tool call / 15s |