Skip to main content
Glama
textbee-mcp

textbee-mcp

Official

Related Servers

Alternatives to textbee-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      AndroidAPI.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 Keys
      52
      39 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      1
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables 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
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to read, organize, and send SMS messages through your ClickSend account.
      -

    TDQS

    A4.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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).

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data