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: 1 tool call per 15 seconds per API key. The error text carries the exact wait:

rate limit exceeded: 1 tool call per 15s, retry in 12s.

Nothing ran β€” the limit is checked before the operation, so no call was placed and no record created. Wait out the window and ask again, one action at a time. 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 API key is missing, malformed, revoked, disabled, or expired.

  • 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 Settings β†’ API Keys if it was revoked.

A tool I expected isn’t in the list

The server only registers the tools your key is entitled to, so a missing tool means your key lacks the scope (or the key tier) for it. Check the scope table and re-issue the key with the needed scopes. Remember the users, plans, and subscriptions tools require a tenant/agency key β€” an account key only ever shows the call tools.

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.