Skip to main content
VoiceInfra exposes a remote MCP server. That means you can work with your VoiceInfra workspace from inside Claude, ChatGPT, or any other tool that supports the Model Context Protocol — asking “list my voice agents” or “why did the last call end early?” without leaving that tool. There is no API key to create and no token to paste. Your client registers itself and you approve access in the browser.
Authentication uses OAuth. You will be asked to sign in and choose a workspace the first time you connect, and you can disconnect at any time.

​
Your MCP address

Every workspace has one address to copy, shown in the portal under Connected apps → Your MCP address. It looks like:
The address is specific to the region your account lives in, because each region is a separate deployment with its own data. Copy it from the portal rather than constructing it by hand.

​
Connecting

1

Add a custom connector

Open Claude → Settings → Connectors → Add custom connector.
2

Paste your address

Paste your MCP address as the URL. Leave the client ID and secret empty — Claude registers itself automatically.
3

Approve access

Click Connect. A window opens asking you to sign in, choose a workspace, and approve the permissions.
4

Try it

Claude will list the tools it can now use. Try something like “list my voice agents”.
If you are using the desktop app you can close the browser window once approval is complete — the connector picks the session up.

​
Approving access

Whichever client you use, the same VoiceInfra screen handles the connection:
  1. Sign in if you are not already signed in.
  2. Choose a workspace — the app acts only within the workspace you pick.
  3. Review the permissions the app asked for, and allow or deny.
Each permission is grouped into an area you will recognise, and shows whether it is view or can change. Anything that spends credit is called out separately. You can grant change access to some areas and leave others read-only. The app’s ability to change anything is still limited by your role in that workspace — see Connected apps.
If the consent screen shows “This app hasn’t been reviewed by VoiceInfra”, the app registered itself and anyone can do that. Its name and logo prove nothing. Only continue if you started the connection from the app yourself and trust it.

​
What you can do from a connected client

Once connected, the client can work with the same resources you can, within the workspace you chose: Actions that change your configuration or spend money respect the same approval rules as elsewhere in the product, and are governed by the permissions you granted.

​
Disconnecting

Open Connected apps in the portal to see every client you have connected, when it was added, and what it can do. Disconnect takes effect immediately — the client stops working right away and anyone using it must connect again.

​
Frequently asked questions

No. The MCP server uses OAuth. Your client registers itself and you approve access in the browser. For programmatic access with a key instead, see the API reference.
Each region is a separate deployment holding its own data. Your MCP address points at the region your account lives in, which is why you should copy it from the portal rather than guess it.
Only the workspace you chose on the approval screen. To work with another workspace, connect again and pick it.
It can only use the permissions you granted. Change access is opt-in per area on the consent screen, and spending credit is always surfaced separately. What it can actually change is also bounded by your workspace role.
No. Using the MCP server is included. Calls and messages you place through it are metered normally.