Key Takeaways
- Windsurf MCP SMS for an Android SMS gateway is an agent tool layer over HTTPS REST — not a Windsurf plugin marketplace product we ship.
- MCP tools should call your thin REST client; live fields stay in Developer Center.
- Agents can burn airtime and plan volume — rate-limit tools and isolate OTP.
- Platform pricing is devices + SMS send volume; Free is 1 device / 300 SMS lifetime; BYO Android and operator credit.
- Accept ≠ delivered; wire DLR or webhooks outside the chat UI.
MCP is a REST wrapper
Search for Windsurf MCP SMS with an Android SMS gateway usually means: can an IDE agent call tools that send texts? Yes — if those tools wrap HTTPS REST to the control plane. That is not a first-party Windsurf plugin, not an MCP “SMS modem,” and not a substitute for a paired Android + funded SIM.
Product path: Android SMS gateway. Live fields: API documentation. Pricing: devices + send volume; Free is 1 device / 300 SMS lifetime; you bring phone and operator credit.
“If the agent can call send_sms without a human gate, it can empty prepaid before you finish the prompt. MCP is power tools over REST — treat it like production API access.”
Windsurf → MCP → API → SIM
What MCP is / is not
| Is | Is not | |
|---|---|---|
| Integration shape | Tools wrapping REST + Bearer token | Official Windsurf plugin SKU from us |
| Send path | Control plane → Android app → SIM | Agent radio / cloud SMSC |
| Schema source | Developer Center | Prompt folklore |
| Delivery proof | DLR / webhooks | Chat “success” text alone |
| Billing | Devices + volume + your airtime | Unlimited free agent SMS |
Tool design
Prefer narrow tools: send_sms, list_devices, maybe OTP helpers — each with hard caps, idempotency keys, and allowlists for destinations in non-prod. Do not expose raw “send anything to anyone” to an unsupervised agent. Related MCP spokes under the MCP cluster stay ops-focused; this page is the Windsurf-shaped overview.
Language samples for humans remain REST (PHP, C#) — not an MCP SDK product.
Keys and agents
API keys stay in the MCP server process env, never in the chat transcript. Rotate on staff change. Separate staging keys so a prompt experiment cannot hit production SIMs. Verify webhook signatures in your backend — agents should not “confirm delivery” by guessing.
Radio still wins
Offline phones, OEM killers, and empty prepaid look like MCP failures. Check device last-seen first. Setup, webhooks. Isolate OTP from promotional tool calls.
Pricing
Every successful tool send can burn operator segments and platform volume. Free: 1 device / 300 SMS lifetime; sends pause when exhausted. See pricing. External MCP protocol context: modelcontextprotocol.io.
Checklist
- MCP server wraps REST only — no fake plugin claim.
- Keys in env; destination allowlist in staging.
- Idempotency on OTP tools.
- Device online + airtime before agent demos.
- DLR/webhook path outside the IDE chat.
Next steps
Developer Center, FAQ, API hub.
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
- Android SMS gateway product guideDefinition, product, and how to buy
- download the Android gateway appGet the APK
