Read BulkSMS messages, replies, profile and webhooks; send SMS to up to 10 numbers. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"bulksms": {
"url": "https://bulksms.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"bulksms": {
"type": "http",
"url": "https://bulksms.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your API token ID and API token secret.
Create a token in BulkSMS under Settings > Developer Settings > API Tokens (not your account password). Sending SMS through this server spends credits from your account. Your token is used only to call the BulkSMS API on your behalf; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your API token ID and API token secret. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the BulkSMS connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
bulksms_get_profile | read | Get account profile and credits Show the BulkSMS account: username, credit balance, credit limit, whether credit transfer is allowed, the daily message quota (size and remaining today) and the sender ids this account may use. Company and billing details are left out. BulkSMS REST: GET /profile. |
bulksms_list_messages | read | List messages List sent (SENT) and received (RECEIVED) SMS messages, newest first by default. BulkSMS limits the window to the last 7 days unless submission_date_from is given. To page newest-first, pass before_id = the smallest id of the previous page; with sort_order ASCENDING pass after_id = the largest id of the previous page. REST: GET /messages with a `filter` built from the arguments. |
bulksms_get_message | read | Get message Get one sent or received message by its id: body, recipient, delivery status, number of parts and credit cost. BulkSMS REST: GET /messages/{id}. |
bulksms_list_replies | read | List replies to a sent message List the received (RECEIVED) replies linked to a sent message id. Only messages sent with a REPLIABLE sender have linked replies. An empty list means none or an unknown id. BulkSMS REST: GET /messages/{id}/relatedReceivedMessages. |
bulksms_list_blocked_numbers | read | List blocked numbers List phone numbers the account may not send to (added via the API, by a recipient replying STOP, or by BulkSMS). To page, pass min_id = the largest id of the previous page + 1. BulkSMS REST: GET /blocked-numbers. |
bulksms_list_webhooks | read | List webhooks List the account's webhooks (name, trigger SENT/RECEIVED, active flag, invoke option). Only the host of each webhook URL is shown: the path and query can hold a secret. Read-only: webhooks are not changed by this server. BulkSMS REST: GET /webhooks. |
bulksms_send_message | write | Send SMS WRITE: SENDS REAL SMS to real people and SPENDS CREDITS from the user's BulkSMS account; it cannot be undone or recalled. One message text to 1 to 10 phone numbers in international format (e.g. +447700900000). Cost = credits per message part x number of parts x number of recipients (about 1 credit per 160-character GSM part to a standard-route destination; the exact cost depends on the destination and appears as creditCost on the sent messages afterwards). Messages longer than one part are concatenated up to max_parts parts (default 3). Non-GSM characters (emoji, accents outside GSM 03.38) are replaced by "?" unless auto_unicode is true, which sends Unicode (shorter parts, more credits). Messages to blocked numbers still cost credits. Only send what the user explicitly asked for, confirm the text and recipients first. No groups, no scheduling. Texts containing BulkSMS template placeholders such as {F0###}, {fn###} or {sn###} are rejected (they would merge contact data). BulkSMS REST: POST /messages. |
bulksms_block_number | write | Block a phone number WRITE: adds ONE phone number to the account's blocked list, so that no further messages are sent to it (a send to a blocked number fails with FAILED.BLOCKED and still costs credits). This API has no way to remove a block again: do it only when the user asks for it. BulkSMS REST: POST /blocked-numbers. |
bulksms_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
bulksms_request_feature | Request a missing feature Tell usefulapi that the user needs something the BulkSMS tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
bulksms_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on BulkSMS (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $19/month or $190/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
bulksms_cancel_subscription | Cancel the Pro subscription Cancel the caller's BulkSMS Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run bulksms_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this BulkSMS server only. Subscribe with bulksms_upgrade (it returns a Stripe Checkout link). Cancel any time with bulksms_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running bulksms_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by BulkSMS. The server calls the BulkSMS API with your own BulkSMS access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your API token ID and API token secret. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your API token ID and API token secret. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the BulkSMS API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in BulkSMS.
Yes, if you approve it. 2 of the 8 BulkSMS tools can create or change data. The other 6 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this BulkSMS server only. Cancel any time: Pro then runs to the end of the paid period. Run bulksms_usage_status to see how many calls you used.
Ask the AI to run bulksms_upgrade: it returns a Stripe Checkout link. To cancel, run bulksms_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with bulksms_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.