Skip to main content
The Vobiz MCP server connects an AI client to your own Vobiz account. With it, Claude (or any MCP client) can:
  • check your balance, billing transactions, live calls and call history
  • place and control calls and conferences, stream call audio to your AI agent, and build VobizXML IVRs
  • manage phone numbers, SIP trunks, credentials, IP allow-lists, SIP endpoints, voice applications and sub-accounts
  • send and track SMS, MMS and RCS messages
It also ships the Vobiz Agent Skills, so the model follows the right endpoints and VobizXML rules.
This server acts on your account. To search the documentation instead, use the Vobiz Docs MCP server. The two work well side by side.

Prerequisites

  • A Vobiz account and its Auth ID and Auth Token, from the overview page of the Vobiz console.
  • Node.js 22.9 or newer for the local options (node --version).

Connect Claude step by step

The hosted connector works in claude.ai, Claude Desktop and the Claude mobile apps. There is nothing to install: you add a URL and sign in with your Vobiz credentials.
1

Copy your Vobiz credentials

Sign in to the Vobiz console. On the overview page, copy your Auth ID (it starts with MA_, or SA_ for a sub-account) and your Auth Token.
2

Open Connectors in Claude

In claude.ai or Claude Desktop, open Settings → Connectors and click Add custom connector.On a Team or Enterprise plan, an Owner adds custom connectors for the organization under Admin settings → Connectors. Members then connect their own Vobiz account in Settings → Connectors.
3

Add the Vobiz MCP server

Enter a name, for example Vobiz, and the URL:
Leave the advanced OAuth fields empty, then click Add.
4

Connect and sign in

Click Connect. A Vobiz sign-in page opens and shows which app is asking for access.
  1. Paste your Auth ID and Auth Token.
  2. Optional: tick Read-only access to let Claude look at your account without placing calls, sending messages or changing settings.
  3. Click Allow access.
You return to Claude and the connector shows as connected.
5

Turn on the tools in a chat

Start a new chat, open the tools menu in the message box and make sure Vobiz is enabled. Then try:
Claude asks before it runs any tool that places a call, sends a message or changes your account, and the server also needs your confirmation for each one.
Your Auth ID and Auth Token are sealed inside the access token that Claude holds. The Vobiz MCP server does not store them.

Change access or disconnect

If something goes wrong

Connect any client in one step

Every client below connects to the hosted server and signs you in on a Vobiz page, so no Auth Token goes in a config file.

npm package

The server is published on npm as @vobiz/mcp and listed in the official MCP Registry as io.github.vobiz-ai/vobiz-mcp. It needs Node.js 22.9 or newer.
MCP clients start the server for you from their config, so you rarely run it by hand. The vobiz-mcp command has three modes: Settings come from environment variables. VOBIZ_AUTH_ID and VOBIZ_AUTH_TOKEN are required for local use. The full list is in .env.example.

Run it locally

To run the server on your own machine instead, pick your client. The local options need Node.js 22.9 or newer.
  1. Download vobiz-mcp-<version>.mcpb from the latest release.
  2. Open the file. Claude Desktop shows the install screen.
  3. Enter your Auth ID and Auth Token, then choose whether Claude may place calls, send messages or change your account.
The Auth Token is stored in your operating system’s keychain.

Turn on actions

With the hosted connector, calling, messaging and account changes are available unless you choose Read-only access when you sign in. Number purchases are not offered there. When you run the server locally (desktop extension, plugin or npx), it reads your account and generates VobizXML out of the box. Calling, messaging and account changes stay off until you enable them: When an action is enabled, the model still has to confirm it with you before running it:
  • Confirmation. Every call, message, transfer, recording, purchase and account change needs your explicit approval (confirm: true), and your client also asks before running it.
  • Idempotency keys. These prevent a retry from calling or texting twice.
  • Server limits. Destination countries, call duration, calls and messages per minute and per hour, concurrency, a balance floor and a spending cap all apply, and each one can be configured.
Calls and messages reach real people and are billed to your account. Enable these capabilities only for clients you trust, and keep the limits tight.

What you can ask

Tools

To load only some groups, set VOBIZ_TOOLSETS, for example VOBIZ_TOOLSETS=calls,records,skills. Set VOBIZ_READ_ONLY=true to keep only read-only tools. SIP passwords, credential secrets and sub-account tokens are always redacted; view or reset them in the console. The hosted connector offers every tool except number purchases and the IVR tools that need a callback server of their own: gather_dtmf, get_gather_result, list_webhook_events, hold_call and unhold_call. Use the npm package in HTTP mode for those. The full input reference for every tool is in the repository.

Skills, prompts and resources

The server bundles the Vobiz Agent Skills and exposes each one three ways:
  • Tools. list_vobiz_skills and get_vobiz_skill work in every client.
  • Prompts. Each skill is a prompt with an optional task. In Claude Code, type /mcp__vobiz__vobiz-voice-xml build an IVR for a clinic.
  • Resources. vobiz://skills/index and vobiz://skills/{name}.

Privacy

The server uses your Auth ID and Auth Token only to call the Vobiz API on your behalf. The hosted connector keeps no credential or conversation database, and logs never contain tokens, message text or phone numbers. It does not read your conversation history or files. See the Vobiz privacy policy.

Troubleshooting

Vobiz Docs MCP server

Search the documentation from your AI client.

Agent Skills

Install the Vobiz skills into your coding agent.

Authentication

Find and rotate your Auth ID and Auth Token.