Botcall MCP Server

Give your AI agent a real phone number for SMS verification codes.

Local serverstdio

What is the Botcall MCP server?

Give your AI agent a real phone number for SMS verification codes. The botcall mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 6 defined tools rather than through you.

What it actually does

An MCP server that gives AI agents real phone numbers. Provision a number, receive SMS, and extract verification codes — all through tool calls.

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at botcall-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Its toolset

Everything the assistant can do here goes through one of these:

  • provision_number — The provision_number tool exposed by this server
  • get_code — Wait for an incoming SMS and extract the verification code. Long-polls until a message arrives or the timeout expires
  • get_inbox — The get_inbox tool exposed by this server
  • list_numbers — The list_numbers tool exposed by this server
  • release_number — The release_number tool exposed by this server
  • get_usage — Get your current plan, limits, and usage stats. No parameters

Configuration

You will need 2 environment variables: BOTCALL_API_KEY, BOTCALL_API_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the botcall mcp server does with a few real requests.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Botcall's toolset — provision_number, get_code, get_inbox and 3 more — is a fair guide to whether it matches your workflow. It is maintained by danecodes; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
provision_numberThe provision_number tool exposed by this server.
get_codeWait for an incoming SMS and extract the verification code. Long-polls until a message arrives or the timeout expires.
get_inboxThe get_inbox tool exposed by this server.
list_numbersThe list_numbers tool exposed by this server.
release_numberThe release_number tool exposed by this server.
get_usageGet your current plan, limits, and usage stats. No parameters.

How to install the Botcall MCP server

{
  "mcpServers": {
    "botcall": {
      "command": "npx",
      "args": ["-y", "botcall-mcp"],
      "env": {
        "BOTCALL_API_KEY": "bs_live_..."
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
BOTCALL_API_KEYCredential the server authenticates with.Yes
BOTCALL_API_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Botcall to provision number.
  • Use Botcall to get code.
  • Use Botcall to get inbox.

Frequently asked questions

It connects Botcall to MCP-compatible AI assistants such as Claude and Cursor, exposing 6 tools (provision_number, get_code, get_inbox, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Botcall directly.