textbee-mcp
OfficialRelated Servers
Alternatives to textbee-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceAndroidAPI.net MCP Connector lets Claude send SMS, WhatsApp messages, and OTPs via your linked Android device or gateway credits. Features * 52 tools covering SMS, WhatsApp, OTP, Contacts, Android devices * Works with Claude Desktop and Claude Code * Install: npx -y androidapi-mcp Setup Set ANDROIDAPI_SECRET env var with your API key from AndroidAPI.net → Tools → API Keys5239 npmMIT
- AlicenseAqualityCmaintenanceEnables AI agents to send SMS from and read incoming messages on a paired Android phone, and to inspect devices, message history, and per-recipient send status.6MIT

BudgetSMS MCP serverofficial
AlicenseNot gradedqualityCmaintenanceEnables Claude, ChatGPT and other MCP clients to send SMS worldwide, simulate sends, check account credit, look up number networks and reachability, check delivery status, and read per-operator pricing through the SMS API.1MIT- FlicenseNot gradedqualityDmaintenanceEnables an AI-powered SMS assistant that receives inbound messages via TextBee, processes them with a local Ollama model and optional MCP tools, and sends replies back to the sender.1-
- FlicenseNot gradedqualityCmaintenanceEnables AI applications to send and receive real iMessage/SMS messages through a local MCP service, with tools for sending texts, checking new messages, browsing history, and querying line status.3-
- FlicenseNot gradedqualityCmaintenanceEnables Claude to read, organize, and send SMS messages through your ClickSend account.-
TDQS
Scored across 3 tools
Each tool occupies a distinct role: send_sms writes, get_messages reads, list_devices enumerates devices. The descriptions explicitly clarify boundaries (e.g. list_devices sends no SMS, get_messages covers all devices without a device id), leaving no realistic chance of misselection.
All three names follow a consistent snake_case verb_noun pattern: send_sms, get_messages, list_devices. The verb choice (send/get/list) is semantically appropriate per tool rather than arbitrary, so the set reads predictably.
Three tools is exactly right for a narrow SMS gateway: send, read, and device discovery, with each tool earning its place. Nothing is padded and nothing feels thin given the constrained domain.
The core lifecycle is covered and cross-referenced well: sms_batch_id from send feeds get_messages, device_id from list_devices feeds send, and pagination/cursor rules prevent dead ends. Minor gaps remain (no account/quota info, no way to enable or disable a device when a send fails with a device error, no message deletion).