smsportal.app MCP server
Related Servers
Alternatives to smsportal.app MCP server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to use a real Android phone with a SIM to retrieve phone numbers, receive SMS verification codes, and manage SMS messages.-
- AlicenseAqualityBmaintenanceSend texts (SMS) and sign-in codes from your own Android phone and your own number from any AI app, check whether they went out, and read replies.7496 npmMIT
- AlicenseCqualityDmaintenanceEnables AI agents to send, receive, schedule, and manage SMS and MMS messages using the Twilio Programmable Messaging API. It provides comprehensive tools for handling bulk messaging, conversation threads, and real-time inbox monitoring through a secure, production-grade architecture.161MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to safely use real Android phones by listing devices, reading screens and UI elements, tapping, typing, launching apps, and running workflows only within allowed permissions and approvals, with every step recorded in an audit log.60 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to manage phone numbers, send/receive SMS, and place voice calls through natural language, connecting to the phone network via the AgentPhone API.28557 npm124MIT

textbee-mcpofficial
AlicenseAqualityAmaintenanceSend and read SMS through your own Android phone via textbee.dev, the open-source SMS gateway. Three tools for Claude, Cursor, and any MCP client: send_sms, get_messages (replies, verification codes, delivery status), list_devices. Self-hosted friendly.3238 npm1MIT
TDQS
Scored across 6 tools
Most tools are distinct, but smsportal_list_messages and smsportal_read_received_sms overlap because both can surface received SMS, and an agent may hesitate over which to use for incoming messages. The descriptions clarify the difference, especially that read_received_sms targets already-synchronized incoming messages, but the boundary is not perfectly crisp.
All tool names use a consistent smsportal_ prefix and snake_case verb_noun structure: list_devices, get_stats, list_messages, read_received_sms, get_send_status, send_sms. The convention is predictable throughout.
Six tools is well-scoped for an SMS portal MCP server, covering the main resources and actions without feeling thin or bloated. Each tool appears to earn its place in the surface.
The tool set covers device listing, stats, message listing, received-message reading, send-status checking, and sending SMS, which is a solid lifecycle for the domain. Minor gaps exist around message-level operations such as marking read or deleting messages, but core workflows are supported.