Skip to main content
Glama
Sign In
agentring

agentring

by mutonby
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to agentring

No user-submitted related servers found.

    Related Servers

    • call-me

      radres
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to ring or text a user's actual iPhone, read a question or update aloud, and return the spoken answer back to the agent as text. Calls and messages land in a single titled thread per agent, with tools for polling results, waiting for replies, and labeling conversations.
      41
      MIT

    • SMSTunnel

      narcisbodea
      A
      license
      A
      quality
      B
      maintenance
      Send texts (SMS) and sign-in codes from your own Android phone and your own number from any AI app, check whether they went out, and read replies.
      7
      496 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.
      -
    • A CallNode MCP server

      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

    • CallRelay

      highsierraloft
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to prepare, authorize, and place real outbound phone calls through an Android SIM gateway, then retrieve recordings, full transcripts, contact memory, and scheduled callbacks. Also supports inbound reception instructions, reusable personalities, and live call management from a private dashboard.
      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.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct action: outbound text (send_message), inbound text (get_replies), outbound voice (call), and health/pairing info (status). The only near-overlap is send_message vs call, but the modality difference (text notification vs live voice call) is stated explicitly, so misselection is unlikely.

    Naming Consistency3/5

    Two tools follow a clean verb_noun pattern (send_message, get_replies) while the other two are a bare verb (call) and a bare noun (status). Still readable and unambiguous, but the convention is mixed rather than predictable.

    Tool Count4/5

    Four tools is a tight, well-scoped surface for a phone-relay server; every tool has a clear role. It sits at the thin end—one or two more (e.g. message history or a cancel/hangup) would round it out without bloat.

    Completeness4/5

    The core loop (send text, read replies, place a call, check relay health) is covered with no obvious dead ends. Gaps are minor: no message/call history beyond the consume-once replies, and no explicit cancel/hangup or delivery-status check.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data

    Resources