Skip to main content
Glama
h-3303

phone-sms

by h-3303
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to phone-sms

No user-submitted related servers found.

    Related Servers

    • openmessage

      MaxGhenis
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for a local-first messaging workspace that integrates Google Messages, WhatsApp, and Signal. It enables reading, sending, searching messages, and managing conversations through MCP tools.
      61
      -

    • imessage_mcp

      jtcorbett
      F
      license
      Not graded
      quality
      C
      maintenance
      Local MCP server for macOS Messages + Contacts: send messages, read chat history, wait for replies, and manage Contacts.app entries.
      1
      -
    • textbee-mcp by textbee

      textbee-mcpofficial

      textbee
      A
      license
      A
      quality
      A
      maintenance
      Send 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.
      3
      46 npm
      1
      MIT

    • 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

    • iMessage MCP Server

      sameelarif
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables reading, searching, and sending iMessages directly from MCP-compatible clients by accessing the local macOS iMessage database, supporting conversations, attachments, and both individual and group chats.
      381 npm
      10
      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

    A3.9/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a clearly distinct action: listing threads, reading a single thread, finding contacts, and sending messages. There is no meaningful overlap between any pair.

    Naming Consistency5/5

    All four tools use a consistent snake_case verb_noun pattern (list_threads, read_thread, find_contact, send_sms). The convention is predictable throughout.

    Tool Count4/5

    Four tools is well-scoped for a focused SMS server, covering discovery, reading, contact lookup, and sending. Slightly minimal but each earns its place.

    Completeness4/5

    Core flows are covered: find contact, list threads, read a thread, send a message. Minor gaps exist around thread management (delete/archive, mark read) but typical agent workflows are supported.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues

    Resources