Skip to Content
MCP Server (Preview)Troubleshooting

Troubleshooting

For Claude Desktop specifically — spawn npx ENOENT, the header-with-a-space problem, and the Linux PATH / HOME fixes — see Connect Claude.

rate limit exceeded on a tool call

The assistant hit the tool-call throttle: 10 read calls per 30 seconds, or 3 write calls per 90 seconds, per credential. The error text is:

rate limit exceeded, please retry shortly.

Nothing ran — the limit is checked before the operation, so no call was placed and no record created. The message does not report the remaining time, so wait out the full window and ask again, spacing out the writes. The same message also appears when your tenant exhausts its daily budget of 500 write tool calls; that window clears after 24 hours. A 429 response (rather than a tool error) means you hit the request limit of 20 requests per 5 seconds instead; the Retry-After header says how long to wait. See Rate Limits.

401 unauthorized

The credential is missing, malformed, revoked, disabled, or expired.

  • If you connected with an API key, confirm the header is exactly Authorization: Bearer dlr_live_… (note the space after Bearer).
  • Use a dlr_live_… key against https://api.dialora.ai/mcp.
  • Re-issue the key from the profile avatar (top right) → API Keys if it was revoked.
  • If you connected by signing in, disconnect the server in your assistant and reconnect to run the sign-in again.

A tool I expected isn’t in the list

The server only registers the tools your credential is entitled to, so a missing tool means it lacks the scope (or the key tier) for it.

  • Missing one specific tool? Check the scope table for the resource scope it needs.
  • Missing all the users, plans, and subscriptions tools? Those require a tenant/agency key — an account key only ever shows the call tools.

If you connected by signing in, reconnect and approve the additional permissions on the consent screen. If you’re using an API key, re-issue it from the profile avatar (top right) → API Keys with the scopes you need.

The assistant doesn’t see the Dialora tools

  • Fully restart the client after editing its config (Claude Desktop must be quit, not just closed).
  • On Claude Desktop, check the MCP log — ~/Library/Logs/Claude/mcp-server-dialora.log (macOS), %APPDATA%\Claude\logs\mcp-server-dialora.log (Windows), ~/.config/Claude/logs/mcp-server-dialora.log (Linux). A spawn npx ENOENT line means the PATH fix in Connect Claude is missing.
  • Verify the URL is https://api.dialora.ai/mcp and reachable from your network.
  • In Claude Code run /mcp, in Cursor check the MCP settings indicator, in ChatGPT confirm the connector is enabled for the conversation.

A call didn’t go through

  • from_number must be a provisioned, active Dialora number in your account, in E.164 format.
  • to_number must be valid E.164 (e.g. +15559876543).
  • Confirm the agent_id belongs to your tenant.

Retried an action and worried about duplicates

create_call, create_user, create_subscription, and update_subscription_plan take an optional idempotency_key. If the assistant passed one, a retry with the same key and body returns the original result instead of creating a second record. Without a key there is no replay protection — ask the assistant to include an idempotency_key when it retries.

Still stuck?

See Getting Support or contact the Dialora team.

Rate Limits