mcp-twilio-sms
Related Servers
Alternatives to mcp-twilio-sms
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for Twilio communications, enabling SMS/MMS sending, message listing, outbound calls, and phone number lookup.MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that connects Twilio to MCP clients, enabling natural language control of SMS, MMS, WhatsApp messaging, voice calls, and phone number management.404 npmMIT
- AlicenseNot gradedqualityAmaintenanceMCP server that provides SMS sending, CSV bulk SMS, and voice calling capabilities via the Vonage API.Apache 2.0
- AlicenseBqualityDmaintenanceMCP server for sending SMS via the SMSPM API. Send transactional SMS from Claude Desktop, Cursor, Windsurf, Cline, or any MCP client.134 npmMIT
- FlicenseAqualityDmaintenanceMCP server for sending SMS messages via SmsManager.cz HTTP API, supporting high, economy, and low delivery gateways.1-
- AlicenseNot gradedqualityDmaintenanceAn MCP (Model Context Protocol) server that lets users send SMS messages through Twilio API directly from Claude Desktop via natural language commands.12 npm5MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: send_sms sends a message, get_sms_status checks delivery status. There is no overlap or ambiguity; the workflow explicitly links them.
Both tools use a consistent verb_noun snake_case pattern (send_sms, get_sms_status). The naming is predictable and easy to understand.
Two tools cover the core send-and-verify workflow, which is focused and appropriate for a minimal SMS server. It is slightly under the typical 3-15 range but each tool earns its place without redundancy.
The surface covers sending an SMS and checking its status, which are the essential operations. Minor gaps exist (e.g., listing sent messages or retrieving full message details), but agents can work around them for the stated purpose.