Skip to main content
The Bolna MCP server connects your AI assistant directly to your Bolna account over the Model Context Protocol. Once connected, you can list and inspect agents, pull call transcripts, run batch campaigns, build and run multi-step workflows, manage dispositions, knowledgebases, phone numbers, SIP trunks, and sub-accounts, check your wallet balance, create or update agents, and place real outbound calls — all from a chat window, no dashboard tab required. It’s hosted at mcp.bolna.ai — there’s nothing to install or run locally. Point your client at the URL with your API key and you’re connected.

Quickstart

Connect Claude, Cursor, Windsurf, Codex, Zed, or any other MCP client in under a minute

​
What you can do

“List my agents”, “what’s my wallet balance?”, “show me the numbers on my account” — quick lookups without opening the dashboard.
“Get the last 5 executions for agent X and show me the transcript for any that failed” — the assistant chains the lookups for you.
“Create a Hindi lead-qualification agent using Sarvam and GPT-4o mini”, “update agent X’s welcome message” — describe the change, the assistant makes the API call.
“Create a batch from this CSV and schedule it for 9am”, “add a disposition that captures appointment_time from the call” — campaign and post-call setup without leaving the chat.
“Create a workflow that calls this agent and, if there’s no answer, retries in an hour then follows up over WhatsApp”, “run this workflow against +91XXXXXXXXXX”, “start a workflow campaign from this CSV of leads” — author, publish, and run per-contact automations, or check where any contact is stuck.
“Buy me a US number and route it to my support agent”, “add this number to my Twilio trunk”, “what did the Acme sub-account spend this month?” — the enterprise and telephony surface, not just agents.
“Create a knowledgebase from our pricing page and check when it’s done processing” — give an agent RAG over a URL without leaving the chat.
“List any pending violations on my account” — see calls flagged for content policy, regulatory, or fraud review.
“How do I set up a webhook?”, “show me the MCP tool list page” — the assistant searches Bolna’s documentation and reads back the actual page content, instead of guessing from training data.

​
How it works

Your client sends your Bolna API key as a Bearer token to https://mcp.bolna.ai/api/mcp. For the 82 account tools, the server checks the key, calls the matching Bolna REST API endpoint, and hands back trimmed JSON your assistant can reason about. search_docs and get_doc skip the account API entirely — they read Bolna’s public documentation (llms.txt and its doc pages) instead.

​
Switching accounts mid-conversation

Every tool also accepts an optional api_key argument that overrides the connected account’s credential for just that one call. This is built for sub-accounts: ask the assistant to list_sub_accounts, grab the key (sa-...) for the one you want, then pass it as api_key on any later tool call to act as that sub-account — no reconnecting required. A sub-account key also works as the primary connection credential from the start, exactly like a main account’s bn-... key.

How the Bolna MCP server connects your AI assistant to your account

No key is stored server-side — it travels with each request. The server is open source; see the GitHub repo for the implementation.

​
Confirm before it acts

23 tools are flagged as destructive in their tool definitions — irreversible deletes, a real-world effect like spending balance or breaking something still in use, or a change to something already published or running. Most clients ask you to confirm before running them: update_agent, delete_agent, start_outbound_call, schedule_batch, delete_batch, delete_disposition, buy_phone_number, delete_phone_number, delete_sip_trunk, delete_sub_account, remove_provider, delete_knowledgebase, rename_workflow, delete_workflow, save_workflow_draft, publish_workflow, run_workflow, delete_workflow_campaign, start_workflow_campaign, pause_workflow_campaign, resume_workflow_campaign, abort_workflow_campaign, and cancel_workflow_execution — see the Tool List for what makes each one destructive.

​
Reference

Tool List

Every tool the server exposes, grouped by agents, calls, batches, dispositions, knowledgebases, phone numbers, SIP trunks, sub-accounts, voice, violations, workflows, workflow campaigns, workflow executions, and account

Prompt Cheatsheet

Copy-paste prompts for common tasks — works in any client, chat-only included

​
For coding agents

Example: Monitoring Dashboard

Requires Claude Code, Cursor, Windsurf, or another agent that can write and run files — use the MCP server to explore your data, then have it build a small dashboard around it

Bolna Skills

A code-native alternative — teaches the same operations to Claude Code, Cursor, and Codex directly, no MCP connection needed