BusySMSBusySMS

Model Context Protocol

An MCP server for your own SMS verification codes

BusySMS exposes 29 tools over the Model Context Protocol, so an AI agent can wait for a two-factor code and carry on — instead of stopping to ask you to read one off your phone. The codes arrive on an Android phone you already own, on a SIM you have verified.

It is not a rented-number pool, and it cannot read anyone else’s messages. That is the point: the code for an account registered to your real number can only be received by that number.

Connect
https://busysms.net/mcp

HTTP transport. Sign in with MCP OAuth (a code to your phone, then Allow), or send a bsk_live_ API key as a Bearer token. The machine-readable tool list is at /.well-known/mcp.json, generated from the same list the server answers tools/list with.

Read your verification codes

sign-in required

The reason the server exists. An agent triggers a sign-in somewhere, then waits for the code to land on a phone you own.

wait_for_code

Waits for the next code to arrive (long-polls about a minute). Call it right after triggering 2FA. Returns nothing rather than a stale code if none comes — a used code costs you an attempt.

get_latest_code

The most recent code, checked once with no waiting.

list_messages

Recent verification messages, newest first, optionally filtered by device or service.

Your phones and account

sign-in required

What is enrolled, what is verified, what is actually online.

list_devices

Your gateway phones with their online and verified state.

get_device

One device in detail — number, app version, last seen.

diagnose_my_gateway

Why codes are not arriving, and what to do about it.

get_my_account

Name, phone, email, org role, member since.

get_my_billing

Trial or active, verified-number count, monthly estimate.

get_my_org

Members, pending invites, your role.

list_my_api_keys

Key prefixes and last use — never the secret.

create_api_key

Mints a REST key. Hands back a one-time link you open yourself; the agent never sees the secret.

send_sms_to_me

Texts your own number. There is no recipient argument.

send_email_to_me

Emails your own address. Same rule.

Ask about the product — no account needed

no account needed

Sixteen tools any assistant can call before anyone signs up, so it can answer accurately instead of guessing at pricing or what the app does.

get_product_overview

What BusySMS is, who it is for, and its limits.

get_pricing

$5 per verified number per month, 7-day trial, what counts as billable.

get_what_gateway_means

Plain language: your phone is the gateway. Not a rented-number pool.

get_getting_started

Install, sign in, verify a SIM, start the gateway, read codes.

get_download_info

Google Play, Chrome Web Store, dashboard links.

get_device_requirements

Android 8.0+ and a SIM you control. No iOS app.

get_api_and_mcp

REST and MCP endpoints, key format, which tools need sign-in.

get_chrome_extension

How the extension fills a code the Android app captured.

get_billing_model

Dual-SIM, gateway-off billing, removing a number.

get_faq

Billing, privacy, API and extension questions.

get_troubleshooting

Not capturing, login OTP, Chrome fill, API 402.

get_sign_in_help

Phone SMS OTP, optional email OTP. No password.

get_safety_and_privacy

What is captured, what is not, and for how long.

get_service_status

Whether BusySMS is up.

get_support_contact

Support email and phone.

get_legal_pages

Terms, privacy, account deletion.

What it costs

The sixteen public tools are free and need no account. Reading your own codes needs a subscription — $5 per verified phone number per month, with a 7-day trial. See pricing or the API docs.