Skip to main content
Ask Claude — or any assistant that speaks MCP — about your calls, batches and usage, and get answers from your own Vodex workspace. No API key to copy, no integration to build. Server address

​
Connecting

The same address works for everyone. Your workspace is identified when you sign in, not by the address, so there is nothing personal to keep secret here. 1. Add the server to your assistant. In Claude, open Customize → Connectors, click + → Add custom connector, and paste the address above. On a Team or Enterprise plan an owner adds it once for everyone, under Organization settings → Connectors → Add → Custom → Web; everyone else then finds it under Customize → Connectors and clicks Connect. If you use Claude Code, run this instead — note there is no API key in the command:
2. Sign in to Vodex. A browser window opens on the Vodex sign-in page. Use the account you normally use for the console — email and password, or Google. 3. Approve the connection. You will see exactly what the assistant will be able to read and which workspace it applies to. Approve, and you are returned to your assistant with the connection live.
Nothing is shared until you approve it on that screen. If a connection request appears that you did not start, cancel it — cancelling grants nothing.

​
What it can see

Can read
  • Calls, their outcomes and transcripts
  • Assistants and how they are configured
  • Batches, their rows and every dial attempt
  • Phone numbers on your account
  • SMS history and webhook deliveries
  • Minutes used against your plan
Cannot do
  • Place a call
  • Send a message
  • Start, pause or cancel a batch
  • Change any setting or assistant
  • Reach any workspace but yours
The second list is enforced at the server, not by asking the assistant to behave: the Vodex-hosted server at mcp.vodex.ai publishes the read tools above and nothing else, so those actions are never offered to your assistant and it cannot take them by mistake.

​
Things worth asking

  • How many minutes have we used this period?
  • Pull my last 50 calls and tell me which failed, and why.
  • Why is my batch running slowly?
  • Which of my assistants has the worst answer rate this week?
  • Did the webhook for event evt_8f2c actually get delivered?
Questions that compare, summarise or explain tend to work better than ones that just fetch a row — reading and interpreting the data is the part an assistant adds.

​
Security

Your assistant is given a credential scoped to your workspace and to reading only. It carries the same access your own console session has, limited to the list above, and every request is checked by Vodex against your account — the connection cannot reach another customer’s data. The credential is short-lived and renews itself quietly in the background, so you should not be asked to approve anything again after the first time.
Disconnecting is not yet self-service. To revoke an assistant’s access, email support@vodex.ai and we will remove it immediately. A screen for managing this yourself is on the way.

​
If something goes wrong

Confirm the address is exactly https://mcp.vodex.ai/mcp, including the /mcp at the end. If your client asks for an API key or a header, it is an older client that cannot do the sign-in flow — see the last item below.
That is expected when you are not already signed in to the Vodex console in that browser. Sign in and the approval screen appears next, with your request intact.
Check you approved the workspace you meant. If you belong to more than one, the connection uses whichever was active when you approved, and the approval screen names it.
Calls are read newest-first, so a question spanning several weeks makes the assistant page back through them. Narrowing the question — one assistant, one batch, a shorter window — is much faster.
Some older MCP clients cannot perform the browser sign-in. Those can connect with a Vodex API key sent as an Authorization: Bearer header instead — the same credential described in Authentication. Email support@vodex.ai and we will help you set that up.