ChatGPT Plugin

BusySMS

Your phones as an SMS gateway

Brand: Unknown

Category: Pending
Primary Subcategory: Vendor API & SDK Integration Connectors

Integration details

Description

BusySMS turns Android phones you already own into a gateway for verification codes. Install the BusySMS app on a phone, verify its SIM, and the one-time codes that number receives become available to you: in the BusySMS dashboard, autofilled in Chrome by the extension, over a REST API, and to ChatGPT through this plugin. With BusySMS connected, ChatGPT can list your verified numbers, read the most recent code, wait for the next code while you trigger a login, explain why a code has not arrived (an offline phone, an unverified SIM, an inactive account), and show who you have shared a number's codes with. BusySMS only ever reaches phones enrolled on your own account, and only the verification and one-time-passcode messages they receive. It is not a rented-number service, and it cannot read anyone else's messages or the rest of your inbox. Built for developers and QA teams who automate sign-in tests, AI-agent builders whose agents stop at a verification code, and teams who share one login number.

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Pending
Primary Subcategory: Vendor API & SDK Integration Connectors
Secondary Subcategories: None listed
Brand: Unknown
Access: Account required
First tracked: 2026-11-05
Tool count: 37
Market: US

Agent DiscoverabilityChatGPT Plugin Discovery Score

ChatGPT organic discovery is live

Your score is coming

ChatGPT now suggests Plugins on its own when they match a user's request.Your Plugin Discovery Score measures how often yours appears, and it will show here as soon as it’s ready.

ChatGPT recommends Airtable when a user asks it to update a CRM. — ChatGPT surfaces Airtable because it matches the user's request.

Primary Subcategory

Competing in ChatGPT Vendor API & SDK Integration Connectors

View Category

Listed in alphabetical order

Primary Subcategory

AWS CoreComing soonGet notified

BirdComing soonGet notified

BusySMSComing soonGet notified

CrowdinComing soonGet notified

InfobipComing soonGet notified

Tools

37 tools agents can invoke

Accept an invite to someone else's number (shareId from list_my_shares → incoming). After accepting, that number's new codes reach you. Only invites addressed to the caller can be accepted. Requires sign-in.
accept_share
Support helper: enrolled vs verified vs online, likely blockers, and next steps. Requires sign-in.
diagnose_my_gateway
BusySMS OTP Autofill on the Chrome Web Store: how it fills website codes after the Android app captures them.
get_chrome_extension
Public support email, phone, terms, privacy, and account-deletion URLs.
get_support_contact
Create a REST API key on the caller's own BusySMS account for use with the /api/v1 endpoints. IMPORTANT — this tool NEVER returns the secret. It returns { id, name, keyPrefix, revealUrl }: the key exists immediately, but its plaintext (bsk_live_…) can only be collected by the human, once, by opening revealUrl in a signed-in browser. That is deliberate: the secret is long-lived and must not enter an AI context, because captured SMS text from third parties also flows through this MCP. Do NOT ask the user to paste the key back to you, and do not attempt to read it another way — you do not need it. If you are writing code or config for the user, insert a placeholder such as BUSYSMS_API_KEY and tell them to paste the real value from revealUrl themselves. Give the key a descriptive name saying what will use it. The reveal link expires in 15 minutes and works once; if it lapses, create another key and revoke the unused one. Prefer the MCP tools over REST for your own calls — only create a key when the user needs external or scripted access. Requires sign-in; limited to a few keys per day.
create_api_key
Where to get BusySMS — Google Play URL, Chrome Web Store OTP Autofill URL, website, and dashboard. Always paste these URLs in replies.
get_download_info
Email YOURSELF a message. Always delivered to the email address on your own BusySMS account — the recipient cannot be chosen. Requires sign-in and an email on your account.
send_email_to_me
Frequently asked questions about BusySMS, billing, privacy, API, and the Chrome extension.
get_faq
Step-by-step: install from Play, phone OTP, verify SIMs, start the gateway, read codes via API/MCP/Chrome.
get_getting_started
The most recent SMS received on your devices: its full text and any code, ready to copy or paste (MCP Apps hosts show a one-click Copy SMS button). Optional filters: deviceId, phone, and service or sender (text contains). Requires sign-in + active billing.
get_latest_sms
The most recent verification code on your devices (single check, no waiting). Requires sign-in + active billing.
get_latest_code
Terms, privacy, and account-deletion URLs.
get_legal_pages
Metadata for YOUR API keys (prefix, created, last used) — never the secret. Requires sign-in.
list_my_api_keys
Your BusySMS account: display name, phone, email, org role, member since. Requires sign-in.
get_my_account
Your billing org: members, pending invites, your role. Requires sign-in.
get_my_org
List your org's SMS-gateway devices (phones running BusySMS), with online/verified state. Requires sign-in.
list_devices
Same as list_devices — your enrolled phones. Requires sign-in.
list_my_devices
Your subscription: trial/active status, verified-device count, monthly estimate, whether API/MCP can read codes. Requires sign-in.
get_my_billing
Your number sharing: invites waiting for you (Accept in the app or dashboard), numbers shared with you, and numbers you share with others (status, who, last read). Read-only. Requires sign-in.
list_my_shares
Detail for one of YOUR devices: phone, verified, sharing/online, app version, last seen. Requires sign-in.
get_device
Android 8.0+ with a SIM you control (Play package net.busysms.app), or an iPhone on iOS 14+ through a Shortcuts automation (automatic from iOS 17).
get_device_requirements
REST /api/v1 and MCP endpoints, API key format, and which tools need sign-in vs public.
get_api_and_mcp
Recent verification/OTP messages captured on your devices, newest first. Optionally filter by device or service. Requires sign-in + active billing.
list_messages
Revoke one of YOUR REST API keys (id from list_my_api_keys) so it stops working at once — e.g. an unused key from create_api_key, or one that leaked. Cannot be undone; create a new key if needed. Requires sign-in.
revoke_api_key
What BusySMS captures (OTP/verification SMS on your own phones) and what it does not (full inbox, other people's numbers).
get_safety_and_privacy
Public operational status of BusySMS (aggregate only — no infra secrets).
get_service_status
Share one of YOUR verified numbers' codes with another person: BusySMS sends them an invite by SMS or email; once they accept, codes texted to that number also reach them (dashboard, apps, Chrome extension, API, MCP). Changes who can read your codes — only call it when the user asked to share with this person. Up to 5 people per number; revoke any time with revoke_share. Requires sign-in.
share_number
Sharing a number's codes with another BusySMS user: how to invite (phone or email, up to 5 per number), how to accept (link, app, dashboard), what they see (only codes after accepting, read-only, labelled "Shared by"), billing (free for them, follows the owner's plan), revoke/leave, and where shared codes appear (dashboard, apps, Chrome extension, API, MCP).
get_sharing_help
EXPLAINS how sign-in works — phone SMS OTP (app + web), optional email OTP on the website, no password. Answers questions ABOUT sign-in, such as why a code has not arrived or whether a password exists. Does NOT sign anyone in: to sign a visitor in, use the `sign_in` page tool, which shows a form in the chat.
get_sign_in_help
End a share (shareId from list_my_shares): as the owner it removes that person's access or cancels a pending invite; as the person it was shared with, it leaves. Immediate. Requires sign-in.
revoke_share
End-to-end check that a phone forwards codes: BusySMS texts a test code to one of YOUR verified numbers and waits (~60s) for that phone (Android app or iPhone automation) to forward it back. Answers arrived yes/no, how long it took, and what to check if it did not. Sends one SMS to your own number (rate-limited). Requires sign-in.
test_my_gateway
Text YOURSELF a message. Always delivered to the phone number on your own BusySMS account — the recipient cannot be chosen. Requires sign-in and a phone on your account.
send_sms_to_me
Common problems and fixes (not capturing, login OTP, Chrome fill, API 402, billing count). Optional topic id filter.
get_troubleshooting
Wait for the next verification code on your devices (long-poll ~60s). Use right after triggering 2FA. With several numbers (or one shared with you), pass phone and/or sender so a code meant for something else is not returned. Requires sign-in + active billing.
wait_for_code
What BusySMS is, who it is for, how the SMS gateway works, and important limits. Use this first for visitors who are not signed in.
get_product_overview
Plain-language: your phone is the gateway. Not a rented-number pool and not intercepting others' SMS.
get_what_gateway_means
iPhone setup, step by step for the person's iOS version: the Shortcuts "Message" automation that forwards codes, with or without the BusySMS iPhone app (beta), the iOS 27 one-link install, the in-app Setup check, and what to do when codes are not forwarded. Pass iosVersion (e.g. "17" or "27.0.1") for just their steps.
get_iphone_setup

FAQs

BusySMS ChatGPT Plugin FAQ

How the directory, categories and Discoverability Score work.

Read the methodology

How do I improve BusySMS's ChatGPT Plugin discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

What are BusySMS alternatives on ChatGPT?

As of 2026-11-05, BusySMS competes with AWS Core, Bird, Crowdin, Infobip, Infra - Oracle PLM (DEV3), Ledger Botje - Exact Online, MCP Server For WordPress, Nonica and 4 more in ChatGPT Vendor API & SDK Integration Connectors, ranked by public Discoverability Score.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.