Skip to content
Bolna AI logo

Bolna AI MCP server

Give your AI assistant 2 tools it can call in Bolna AI, over one server URL.

Bolna AI is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Tools
2
Works with
Any MCP client
Auth
API key
License
MIT, open source
Updated
September 2026

About the Bolna AI MCP server

Connect Bolna AI once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches Bolna AI and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

Bolna AI tools your AI can run

Once connected, your assistant can call any of these Bolna AI actions by asking in plain language.

  • Make Phone Call

    Initiate an outbound phone call from a Bolna Voice AI agent to a recipient.

    5 fields

  • Custom API Call

    Make a custom API call to a specific endpoint

    10 fields

Triggers

Bolna AI events your agent can watch

These start a run the moment something happens in Bolna AI, so work gets picked up on its own.

  • Call Completion Report

    Triggers when Bolna call report it is completed

    1 field

Give your assistant Bolna AI

Connect Bolna AI once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.

Bolna AI MCP, answered.

No. That is the point of it. One Activepieces server exposes Bolna AI alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect Bolna AI in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 2 tools, including Make Phone Call, Custom API Call, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.