Key Takeaways
- MCP for SMS is a setup of tools that call the same Android SMS gateway REST API — not a first-party Cursor or Claude plugin.
- The host (Cursor, Claude Desktop, etc.) spawns your wrapper. The wrapper POSTs /messages with Bearer from env.
- Confirm live JSON in Developer Center. MCP does not invent a second send contract.
- Start with list-devices. Add allowlisted send later. Keep OTP on your backend.
- You bring the phone and operator credit. Platform pricing is devices plus send volume.
MCP is a door, not a radio
Concepts: MCP for SMS concepts. Spec: Model Context Protocol. API hub: Android SMS gateway API. Live JSON: Developer Center.
Vs REST: MCP vs REST walkthrough. We meter devices and volume.
Host, wrapper, HTTPS
A host loads an MCP server command. That process calls POST https://app.sms-gateway.app/api/v1/messages with env Bearer. The Android is still your paired modem. Pairing.
“If you cannot explain the send without saying MCP, you do not have a protocol problem. You have a missing HttpClient.”
Walkthrough checkpoints
| Step | Pass | Fail |
|---|---|---|
| Env key | Child process sees it | Pasted in chat |
| First tool | list devices | Open send_campaign |
| Send | Allowlisted MSISDN | Any to[] |
| OTP | Backend REST | Agent retries codes |
| Status | DLR | 200 = delivered |
What this is not
Not a Cursor marketplace listing from us. Not Claude Desktop’s official SMS extension. Auth: MCP auth. Webhooks still: webhooks.
Then narrow the tools
Next steps
Wire staging env. Prove list-devices. One staff SMS. Operator credit stays yours.
Related product pages
Jump to the live product docs for this topic—not another long-form article.
- SMS API documentationLive endpoint reference
- device and SMS volume pricingPlans and allowances
- device setup guidePair and go live
- download the Android gateway appGet the APK
