Key Takeaways
- create webhook via MCP concepts: the tool registers POST /webhooks. Your app still verifies HMAC and returns 2xx fast.
- Not a first-party Cursor/Claude plugin. REST wrapper only.
- Confirm live webhook fields in Developer Center.
- Priced by devices and SMS send volume. You use your own phone and operator SMS credit.
- Free 300 SMS lifetime is enough to fire a test event.
- Sibling: /webhook for the product surface.
Concepts for create webhook via MCP are a thin map onto the webhooks REST. Product: SMS webhooks. Overview: MCP overview concepts. MCP specification.
Priced by devices and SMS send volume. You use your own phone and operator SMS credit.
If the agent “created a webhook” and your handler still dumps full SMS text into Discord, MCP did not fail. Your redaction did.
A tool that POSTs /webhooks
URL, events, secret stored like any other key. Developer Center. No invented /api/hooks.
What the wrapper must not skip
| Step | MCP tool | Your app |
|---|---|---|
| Register URL | Yes, via REST | HTTPS endpoint exists |
| HMAC | Pass secret from env | Verify X-SmsGateway-Signature |
| Fast 2xx | — | Queue work; do not block |
| OTP text | Do not echo | Redact in store |
HMAC still lands on your app
Skew window. Idempotent jobs. MCP keys.
Not a marketplace webhook tile
Not a first-party Cursor/Claude plugin. Your wrapper, your URL.
Do not subscribe OTP bodies to Slack
OTP ids only.
Overview vs this spoke
Architecture on the overview. This page is one tool.
Checklist
- Docs fields, not guesses.
- Secret in vault.
- Receiver verifies HMAC.
- 2xx then async.
- No plugin branding.
- Test event on a staff send.
Next steps
Wire the receiver, then canary. Devices + volume.
Related product pages
Jump to the live product docs for this topic—not another long-form article.
- SMS webhook integrationInbound and status events
- SMS API documentationLive endpoint reference
- device and SMS volume pricingPlans and allowances
- Android SMS gateway product guideDefinition, product, and how to buy
