OpenClaw is a multi-channel AI agent gateway (WhatsApp, Telegram, Discord, Slack, iMessage, and more). Because CallingBox already ships a hosted MCP server, wiring it into OpenClaw is a single config entry — OpenClaw-backed agents can then place calls, fetch transcripts, and manage numbers through natural language.
Prerequisites
Register the server
OpenClaw stores outbound MCP servers under mcp.servers in its config. The hosted CallingBox endpoint speaks Streamable HTTP with a bearer token, which maps directly onto OpenClaw’s streamable-http transport.
Option A — CLI one-liner
openclaw mcp set callingbox '{"url":"https://mcp.callingbox.io/mcp","transport":"streamable-http","headers":{"Authorization":"Bearer sk_live_your_api_key_here"}}'
Option B — edit ~/.openclaw/openclaw.json
{
"mcp": {
"servers": {
"callingbox": {
"url": "https://mcp.callingbox.io/mcp",
"transport": "streamable-http",
"headers": {
"Authorization": "Bearer sk_live_your_api_key_here"
}
}
}
}
}
Verify
openclaw mcp list
openclaw mcp show callingbox --json
openclaw mcp set only writes to OpenClaw config. It does not connect to the server or validate reachability — that happens the first time an OpenClaw runtime actually invokes a tool.
What you get
Once registered, OpenClaw runtimes can call every tool exposed by the CallingBox MCP server, including create_call, make_call_and_wait, list_numbers, and purchase_number. See the full list in the MCP Server tools reference.
