SMS and messaging apps APIs and MCP servers for AI agents
Send and receive SMS and messages on WhatsApp, LINE or Telegram through a messaging provider's API.
10 sms and messaging apps APIs an AI agent can call: auth method and header, official MCP server (8), free tier (3), docs links. Machine-readable JSON included. Agents: fetch catalog/sms-messaging.json instead of parsing this page. Last checked 2026-09-24.
Ratings and usage (★) fetched: .
| Service | What an agent can do | Auth | MCP server | Free tier | Details (with sources) | Notes | Proof (ratings, usage) |
|---|---|---|---|---|---|---|---|
| AWS End User Messaging SMS | Send SMS, MMS and voice messages and manage sender numbers, opt-outs and registrations via the AWS SMS and Voice v2 API. | cloud IAMAWS Signature Version 4 with IAM credentials (use an AWS SDK or CLI: aws pinpoint-sms-voice-v2 send-text-message) | official | Paid only; US SMS $0.00774/message + $0.00421 carrier fee (10DLC or toll-free) | Base URL: https://sms-voice.{region}.amazonaws.com Free plan: none ↗ Rate limits: SendTextMessage 1 request/s per region by default (raisable); 1 msg/s per recipient; sandbox $1/month spend ↗ MCP tools: 8: aws___run_script, aws___search_documentation, aws___read_documentation, aws___retrieve_skill, aws___list_regions, aws___get_regional_availability … ↗ | New accounts start in a sandbox: $1/month spend limit, up to 10 verified destination numbers. Production access needs an AWS Support case (reviewed, about 24 h). US sending needs a registered 10DLC or toll-free number. SendTextMessage defaults to 1 request/s per region. The AWS MCP Server is generic (calls any AWS API). | — |
| Bird (formerly MessageBird) | Send SMS, email and WhatsApp messages, verify phone numbers and track delivery via REST API or hosted MCP. | API key / OAuthAuthorization: Bearer bk_<region>_... workspace API key (dashboard), or OAuth 2.0 user token (auth code + PKCE or device flow) | official | Paid only; prepaid wallet, US long code or toll-free $0.0035/SMS + carrier fees | Base URL: https://us1.platform.bird.com/v1 (or https://eu1.platform.bird.com/v1) Free plan: none ↗ Rate limits: Per-organization regional policies (e.g. sms_send); quota in RateLimit-Policy header; 429 with Retry-After ↗ Async jobs: POST /v1/sms/messages returns 202 Accepted with a message id; final status via webhooks or GET ↗ OAuth scopes: sms:write, sms_management:write, numbers:write ↗ MCP tools: 14: sms_send, sms_send_batch, sms_get, sms_list, sms_list_events, sms_senders_create … ↗ | SMS draws on a prepaid wallet (402 if empty). Destination countries are default-deny except your home country; enable more in the dashboard. US long codes need 10DLC registration; the US has no alphanumeric senders. Hosted MCP uses OAuth; a local stdio MCP runs via the bird CLI (bird mcp). | — |
| LINE Messaging API | Lets an agent send and reply to messages, rich messages and broadcasts to users of a LINE Official Account and read user profiles. | API keyAuthorization: Bearer <CHANNEL_ACCESS_TOKEN> (issued for the Messaging API channel in LINE Developers Console) | official | Free Communication plan (Japan): 200 push/broadcast messages/month; reply messages are unlimited. Beyond that only paid plans (Light JPY 5,000 for 5,000 messages, Standard JPY 15,000 for 30,000). Free quotas vary by region | Base URL: https://api.line.me Free plan: 200 messages (Communication plan, Japan), per month, no card ↗ Example call: send a push message: POST https://api.line.me/v2/bot/message/push ↗ Unit price: Japan Standard plan (JPY 15,000/mo incl. 30,000 messages): additional push messages up to JPY 3 each, counted per recipient; reply messages are free ↗ MCP tools: 13: push_text_message, push_flex_message, broadcast_text_message, broadcast_flex_message, get_profile, get_message_quota … ↗ | Requires a LINE Official Account and a Messaging API channel. MCP server is local (stdio, npx @line/line-bot-mcp-server) with channel token and user ID env vars. | — |
| Plivo | Send and receive SMS and MMS worldwide and check delivery status via REST API. | API keyHTTP Basic auth: Auth ID as username, Auth Token as password (from Plivo console) | official | Trial: $10 free credits, no card; then paid per message (US long code $0.0077/SMS + carrier surcharge) | Base URL: https://api.plivo.com/v1/Account/{auth_id} Free plan: $10 in free credits, one-time, no card ↗ Rate limits: 300 requests per 5 seconds; 429 when exceeded ↗ Example call: send an SMS: POST https://api.plivo.com/v1/Account/{auth_id}/Message/ ↗ Unit price: US outbound SMS: long code $0.0077, toll-free $0.0079 per message, plus carrier surcharge $0.0035-$0.0050 ↗ MCP tools: 6: send_sms, make_call, create_application, create_endpoint, get_cdr, get_mdr ↗ | Signup needs a business email and phone verification. Trial accounts can only message verified sandbox numbers, no alphanumeric sender IDs. US A2P traffic needs 10DLC or toll-free registration. The MCP at plivo.com/docs/mcp only searches docs. | — |
| Sinch | Send and receive SMS (and WhatsApp, RCS and other channels) via the Conversation REST API. | API keyAccess key ID + secret (dashboard > Access keys): HTTP Basic, or exchange at https://auth.sinch.com/oauth2/token (client credentials) for a Bearer token | official | Trial: free trial credit and a free test number on signup, no card; then paid (US 10DLC $0.0078/SMS + carrier fees) | Base URL: https://{region}.conversation.api.sinch.com (region: us, eu, br) Free plan: Trial credit and one free test number on signup, one-time, no card ↗ Rate limits: 800 requests/s per project; app queue drains to channel at 20 msg/s by default; 429 when exceeded ↗ Example call: send an SMS via the Conversation API: POST https://{region}.conversation.api.sinch.com/v1/projects/{project_id}/messages:send ↗ Unit price: US SMS (10DLC or toll-free): $0.0078 per outbound message, plus carrier fees ↗ MCP tools: 11: send-text-message, send-media-message, send-template-message, send-choice-message, send-location-message, list-conversation-apps … ↗ | The standalone SMS API is only for existing customers; new accounts send SMS through the Conversation API with an SMS channel. The trial test number can only text your own verified numbers. US A2P needs 10DLC or toll-free registration. MCP server (npm @sinch/mcp) is a developer preview, run locally or self-hosted. | — |
| Telegram Bot API | Send/receive messages, media, and inline interactions via a simple HTTPS bot API. | API keytoken in URL path: https://api.telegram.org/bot<token>/METHOD | community | free, no key needed beyond a bot token from @BotFather | Base URL: https://api.telegram.org/bot<TOKEN> Free plan: free_tier, no card ↗ Rate limits: ~1 message/s per chat, 20 messages/min per group, ~30 messages/s for bulk; paid broadcasts up to 1,000/s ↗ Example call: send a text message: POST https://api.telegram.org/bot{token}/sendMessage ↗ MCP tools: 6: send_message, reply_to_message, edit_message, list_chats, send_file, download_media ↗ | No single official SDK (community libraries only); a self-hosted local Bot API server option removes some file-size limits. Listed MCP server uses a user account via Telethon/MTProto (API_ID/API_HASH + session string from my.telegram.org), not the bot token. | GitHub 1,692★ chigwell/telegram-mcp |
| Telnyx | Send and receive SMS, MMS, RCS and WhatsApp messages and manage phone numbers via REST API. | API keyAuthorization: Bearer <TELNYX_API_KEY> (Mission Control Portal > API Keys) | official | Trial: free testing credits on signup (amount not published); then paid (US 10DLC $0.004/SMS part + carrier fees) | Base URL: https://api.telnyx.com/v2 Free plan: Free testing credits for new accounts (amount not stated), one-time ↗ Rate limits: Send rate per sender: long code 0.1 msg/s (non-US), toll-free 20 msg/s, short code 1,000 msg/s; excess is queued ↗ Async jobs: Send is queued; delivery progress and final status arrive via messaging webhooks ↗ Example call: send an SMS: POST https://api.telnyx.com/v2/messages ↗ MCP tools: 3: list_api_endpoints, get_api_endpoint_schema, invoke_api_endpoint ↗ | US A2P messaging needs 10DLC registration; US long-code throughput is set per 10DLC campaign. Default send rates: long code 0.1 msg/s (non-US), toll-free 20 msg/s per number. Agents can sign up via a bot-challenge flow (telnyx.com/agent-signup.md). | — |
| Twilio | Send/receive SMS, WhatsApp messages, and voice calls programmatically via REST API. | API keyBasic auth: AccountSID:AuthToken (or API Key SID:Secret) | official | Trial: 100 SMS, 100 WhatsApp, 3,000 emails, 75 voice minutes; no card; one-time on signup, expires after 30 days | Free plan: 100 SMS, 100 WhatsApp messages, 3,000 emails, 75 voice minutes; expires after 30 days; only up to 5 verified numbers, one-time, no card ↗ Example call: send an SMS: POST https://api.twilio.com/2010-04-01/Accounts/{AccountSid}/Messages.json ↗ Unit price: SMS to Poland: $0.0457 per outbound segment (mobile numbers and alphanumeric sender IDs); $0.001 fee per failed message ↗ MCP: docs-only: the server searches documentation, it cannot call the API ↗ | Trial accounts can only message verified numbers; US SMS at scale requires A2P 10DLC registration. Hosted MCP is read-only docs/API-spec search; the executing server is Twilio Labs' npm @twilio-alpha/mcp (alpha). | GitHub 111★ twilio-labs/mcp SourceForge 4.8★/13 reviews |
| Vonage API | Send SMS, make voice calls, and build video apps via a unified communications REST API. | API keyAPI key+secret for SMS/Number Insight; JWT bearer token for Voice/Video APIs | official | trial/test credit on signup, then pay-as-you-go | Example call: send an SMS: POST https://rest.nexmo.com/sms/json ↗ Unit price: SMS to Poland: $0.04843 per outbound message ↗ MCP tools: 8: balance, list-applications, create-application, search-available-numbers, SMS, whatsapp-send-text … ↗ | Auth method differs per sub-API (API key/secret vs JWT), which agents must account for. | — |
| WhatsApp Business Cloud API | Send/receive WhatsApp messages, template messages, and media programmatically via Graph API. | OAuth 2.0Authorization: Bearer <system-user access token> | community | Free: non-template (service) messages inside an open 24h customer service window; template messages billed per message (per-message pricing since 2025-07-01) | Free plan: Non-template messages inside an open 24h customer service window are free; template messages billed per message ↗ Rate limits: Up to 80 messages/s per business phone number by default (upgradable) ↗ OAuth scopes: whatsapp_business_messaging, whatsapp_business_management ↗ Example call: send a text message: POST https://graph.facebook.com/v25.0/{phone-number-id}/messages ↗ Unit price: Non-template messages inside an open customer service window are free; template messages are charged per delivered message at rates by category and recipient country (rate cards linked on page) ↗ MCP tools: 9: send_text_message, send_image_message, send_template_message, get_message_templates, create_message_template, upload_media … ↗ | Requires Meta Business verification and pre-approved message templates for outbound marketing/utility messages outside the 24h session window. | GitHub 6,310★ lharries/whatsapp-mcp |
Other categories
- Web search
- Web scraping and browser automation
- Knowledge and research data
- Image generation and editing
- Video generation and editing
- Speech and audio
- Music generation
- 3D generation and assets
- Architecture, CAD and BIM
- Diagrams and software architecture
- Design and UI
- Documents, OCR and presentations
- Translation and language
- Code execution sandboxes
- Developer platforms and DevOps
- Cloud and hosting
- Databases
- Vector search, memory and RAG
- Email, team chat and notifications
- Voice agents and telephony
- Productivity and workspace
- CRM, support and marketing
- Social media
- Maps, geolocation and weather
- Finance, payments and market data
- E-commerce
- Automation and integration platforms
- Model APIs and inference