How to connect Claude, ChatGPT and other AI assistants to your SMS codes

What you need

• An Android phone with the BusySMS app and your number verified. An iPhone works too, through a Shortcuts automation.
• A BusySMS account with an active trial or subscription. The first 7 days are free.
• An assistant that supports remote MCP servers: Claude, ChatGPT, Claude Code, Cursor, VS Code, OpenAI Codex, Gemini CLI and many more.

Claude (web and desktop)

1. 1

   Open connectors

   In Claude, go to Customize → Connectors, click + Add and choose Add custom connector.

2. 2

   Add BusySMS

   Name it BusySMS, paste https://busysms.net/mcp as the server URL and click Continue.

3. 3

   Sign in

   Keep the OAuth sign-in Claude detects. A BusySMS window opens: enter your email address (or the phone number on your account), type the code we send you and press Allow.

4. 4

   Use it in a chat

   Click + at the bottom left of a chat, open Connectors and check that BusySMS is switched on.

The connector works in the Claude desktop app too. On Team and Enterprise plans an owner adds it once under Organization settings → Connectors, and members click Connect.

ChatGPT

1. 1

   Turn on Developer mode

   In ChatGPT on the web, open Settings, find Developer mode under the security settings and switch it on. Without it there is no field for a server URL.

2. 2

   Add a custom MCP server

   Go to Plugins, click + and choose to add a custom MCP server.

3. 3

   Fill in BusySMS

   Name it BusySMS, enter https://busysms.net/mcp under Connection, keep OAuth as the authentication, confirm the warning and click Create.

4. 4

   Sign in and use it

   Sign in with your email address (or the phone number on your account) and press Allow. Then start a new chat and mention BusySMS in your request.

At the time of writing, custom MCP servers work in ChatGPT on the web, not in the mobile apps or in temporary chats. Which plans include Developer mode has changed more than once, so if you do not see the option, check OpenAI's help centre.

Claude Code, Cursor, VS Code, Codex and Gemini CLI

Coding tools add the same URL in their own way. Pick yours:

claude mcp add --transport http busysms https://busysms.net/mcp

{
  "mcpServers": {
    "busysms": { "url": "https://busysms.net/mcp" }
  }
}

{
  "servers": {
    "busysms": { "type": "http", "url": "https://busysms.net/mcp" }
  }
}

codex mcp add busysms --url https://busysms.net/mcp

gemini mcp add --transport http busysms https://busysms.net/mcp

Each one opens a browser window the first time a BusySMS tool is used, for the same sign-in. In Claude Code, run /mcp to sign in straight away.

Try it: ask for a code

Once connected, there are no special commands to learn. Ask in plain words and the assistant picks the right tool:

Open example.com and sign in with +44 7700 900123.
When it asks for the SMS code, use BusySMS wait_for_code
for that number, type the code in and tell me when you are in.

What is the latest verification code BusySMS received?

Show me the last SMS my bank sent, in full.

My codes stopped arriving. Ask BusySMS what is wrong
with my gateway and tell me what to fix.

Keeping it safe

• Your numbers only. The assistant sees codes from your own numbers and numbers shared with you, never anyone else's.
• A text is just text. Anyone can write an SMS, including one that contains instructions. Ask the assistant to use codes, not to act on what messages say, and keep it on tasks you would do yourself.
• No secrets in the chat. If an assistant creates an API key for you, it gets a one-time link that you open yourself, never the key.
• Easy to remove. Delete the connector in your assistant's settings when you no longer need it.

No OAuth? Use an API key

A few clients cannot sign in with OAuth. They can send a BusySMS API key instead: create one under REST API in the dashboard and send it as Authorization: Bearer bsk_live_…. In Claude, that goes under Request headers when you add the connector.

A key can read codes but cannot change anything: sharing a number, testing your gateway and revoking keys all need a signed-in session.

FAQ

Frequently asked questions