Skip to main content
Glama
Sign In
narcisbodea

SMSTunnel

by narcisbodea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to SMSTunnel

No user-submitted related servers found.

    Related Servers

    • 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.
      -
    • A CallNode MCP server by cnchg

      A CallNode MCP serverofficial

      cnchg
      A
      license
      Not graded
      quality
      C
      maintenance
      Lets an AI assistant read call and message history, send texts and picture messages, reach Phone Book contacts by name, and — once switched on — place calls run by a voice agent, all limited to the phone numbers the user ticks. Hosted remotely with OAuth sign-in, so nothing needs to be installed locally.
      MIT

    • Twilio MCP Server

      griffinwork40
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI-powered SMS messaging through Twilio with automatic conversation threading, message status tracking, and webhook support for receiving inbound messages.
      58 npm
      1
      MIT
    • ReadySMS MCP Server by ReadySMS

      ReadySMS MCP Serverofficial

      ReadySMS
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables sending SMS messages, managing contacts, campaigns, and inbox from AI assistants like Claude and ClickUp.
      33 npm
      MIT
    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.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool occupies a distinct action+resource slot: two send variants (regular SMS vs sign-in code, with explicit rules telling the agent which to pick), plus status lookup, device listing, usage, and inbox reading. The send_sms/send_sign_in_code boundary is the only potential overlap and the descriptions resolve it decisively (digits-only codes, separate allowance). No two tools could be reasonably confused.

    Naming Consistency5/5

    All six names follow a strict verb_noun snake_case pattern (send_sms, send_sign_in_code, get_message_status, list_phones, get_usage, list_received_texts). Verbs are used semantically consistently: send_ for outbound actions, get_/list_ for read-only lookups, and read-only tools are labeled as such in their descriptions.

    Tool Count5/5

    Six tools is tightly scoped to the SMS domain: two send paths, status, device selection, quota, and inbox. Nothing feels padded, and no obvious operation is crammed into an overloaded tool. Deliberately omitting a bulk-send tool in favor of one-recipient calls is a defensible design choice given the approval workflow.

    Completeness4/5

    The core lifecycle is covered: send, verify delivery, discover devices, check quota, read replies. Minor gaps remain: there is no way to cancel or list queued/sent messages (only per-messageId status), which matters since texts can sit pending while a phone is offline, and no contact/number validation helper beyond defaultCountryCode. Agents can work around these by asking the user, so it is not a blocking gap.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources