Skip to main content
Glama
textbee

textbee-mcp

Official
by textbee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to textbee-mcp

No user-submitted related servers found.

    Related Servers

    • AndroidAPI net MCP

      TecniForge
      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

    • imessageMCP

      nikonotnicotine
      A
      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.
      912 npm
      MIT

    • clicksend-mcp

      smb333288-wq
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to read, organize, and send SMS messages through your ClickSend account.
      -

    • smspm-mcp

      alesav
      A
      license
      B
      quality
      D
      maintenance
      MCP server for sending SMS via the SMSPM API. Send transactional SMS from Claude Desktop, Cursor, Windsurf, Cline, or any MCP client.
      1
      34 npm
      MIT

    • Phone MCP

      mjrafg
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to use a real Android phone with a SIM to retrieve phone numbers, receive SMS verification codes, and manage SMS messages.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a completely distinct purpose: sending SMS, reading messages, and listing devices. The descriptions clearly delineate when to use each, with no overlap in functionality.

    Naming Consistency5/5

    All three tools follow a consistent verb_noun pattern with snake_case: send_sms, get_messages, list_devices. This makes the API predictable and easy to navigate.

    Tool Count5/5

    The server is tightly scoped to core SMS operations, and three tools fully cover that scope. Each tool earns its place—there is no redundancy or unnecessary bloat.

    Completeness5/5

    The tool set covers the essential SMS workflow: sending, reading (including delivery status), and device management. For a narrow SMS gateway, there are no obvious gaps that would hinder an agent.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources