Early access: the dashboard, CLI, MCP server and REST API are available. We are happy to help you set them up for your voice stack.

MCP server

Manage numbers straight from Claude Code, Codex, Cursor or any other MCP client.

Through the MCP server, your AI assistant orders numbers, connects them to your agent and sets up transfers and hold music. You say in one sentence what you need, and the assistant calls the right tools.

The server runs locally via npx @trunkbeam/mcp and requires Node.js 22 or newer. Create the API key in the dashboard under API, CLI & MCP and pass it as the environment variable TRUNKBEAM_API_KEY.

Tools

ToolWhat it doesPermission
trunkbeam_accountAccount, verification status, plan and the key’s permissionsRead
trunkbeam_pricesPlans and pricesRead
trunkbeam_list_sitesSites; only verified sites get local numbersRead
trunkbeam_search_area_codeSearch an area code by place or codeRead
trunkbeam_list_numbersYour numbers with targetRead
trunkbeam_order_numberOrder a local or 032 number, asks firstOrder
trunkbeam_list_number_requestsOrders and their statusRead
trunkbeam_release_numberCancel a number, asks firstOrder
trunkbeam_connect_number_elevenlabsConnect a number to ElevenLabs in one stepManage
trunkbeam_set_number_targetRoute a number to any SIP addressManage
trunkbeam_set_number_agent_fallbackFallback number if the agent is unreachableManage
trunkbeam_list_connectionsAgent connections (SIP targets)Read
trunkbeam_create_connectionCreate an agent connectionManage
trunkbeam_delete_connectionDelete an agent connectionManage
trunkbeam_provider_guideSetup guide per provider with your real valuesRead
trunkbeam_get_transfer_policyShow transfers to peopleRead
trunkbeam_set_transfer_policyChange transfers, as default or per numberManage
trunkbeam_reset_number_transfer_policyDelete a number’s own transfer settingsManage
trunkbeam_list_hold_musicHold music with descriptions, so the assistant can pick a fitting trackRead
trunkbeam_list_callsRecent callsRead
trunkbeam_usageUsage and cost for a monthRead

Ordering and cancelling always take two steps. First the assistant fetches a quote with the price and shows it to you. Only after you agree does it confirm. The server rejects a confirmation without a prior quote.

Claude Code

claude mcp add trunkbeam \
  -e TRUNKBEAM_API_KEY=tb_live_… \
  -- npx -y @trunkbeam/mcp

With --scope user the server is available in all projects. With --scope project it goes into the repo’s .mcp.json and so to your whole team, but then the key does not belong in the file. Check with:

claude mcp list

Codex

codex mcp add trunkbeam \
  --env TRUNKBEAM_API_KEY=tb_live_… \
  -- npx -y @trunkbeam/mcp

Or directly in ~/.codex/config.toml:

[mcp_servers.trunkbeam]
command = "npx"
args = ["-y", "@trunkbeam/mcp"]

[mcp_servers.trunkbeam.env]
TRUNKBEAM_API_KEY = "tb_live_…"

Check with codex mcp list.

Cursor, Claude Desktop and others

In .cursor/mcp.json in the project, ~/.cursor/mcp.json for all projects, or for Claude Desktop in claude_desktop_config.json:

{
  "mcpServers": {
    "trunkbeam": {
      "command": "npx",
      "args": ["-y", "@trunkbeam/mcp"],
      "env": { "TRUNKBEAM_API_KEY": "tb_live_…" }
    }
  }
}

Windsurf and most other clients read the same mcpServers block.

Keys for assistants

Give your assistant its own key with limited validity. For looking things up, the Read permission is enough. It needs Manage to change targets or transfers, and Order only if it really may buy numbers. You can revoke a key in the dashboard at any time.

Example

Get us a number for our Schramberg site and connect it to our ElevenLabs agent.

The assistant lists the sites, fetches the quote for a local number in area code 07422 and asks you about the price. After your OK, it orders, connects the number to ElevenLabs and shows you what to enter at ElevenLabs.

Connect your stack to TrunkBeam