/v1 API as Model Context Protocol tools. Point any MCP client at it with your API key and your agent can place phone calls and manage phone numbers through natural language.
Connect your MCP client
Official MCP URL: https://mcp.callingbox.io/mcp- Create an API key in the dashboard under Keys.
- Add the server to your MCP client’s configuration:
Authorization header is required on every request. The MCP server is stateless and forwards your key to the Callingbox backend on each tool call.
Tools
Calls
| Tool | Description |
|---|---|
create_call | Place an outbound AI phone call. Returns the created call record immediately. |
list_calls | List calls for the authenticated organization. |
get_call | Fetch a call by ID with status, result, and returns. |
get_call_transcript | Fetch the ordered transcript segments and a rendered plain-text transcript for a call. |
wait_for_call | Poll an in-progress call until it reaches a terminal status. |
make_call_and_wait | Place a call and return the final result in one shot. The most useful tool for agents. |
Numbers
| Tool | Description |
|---|---|
list_numbers | List phone numbers owned by your organization. |
search_available_numbers | Search purchasable numbers by country, area code, and type. |
purchase_number | Buy an available number. |
Build your own agent
Any MCP-compatible client library works. Here’s a minimal example usingmcp-use and OpenAI:
make_call_and_wait, passes the appropriate prompt and returns schema, and waits for the call to complete before returning.
The MCP server currently exposes a prompt-centric shape for convenience. It accepts a
prompt and returns in the tool call and handles the translation to CallingBox’s agent-based /v1/calls under the hood. For full control (persona, tools, reusable instructions, inbound routing), use the Python or TypeScript SDK and the agents API directly.