Skip to main content
Glama
hail

hail

Official

Related Servers

Alternatives to hail

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Make phone calls and join Zoom, Microsoft Teams and Google Meet meetings from any AI agent. A self-hosted, open-source voice agent that calls businesses and people through your own SignalWire or Twilio number, joins meetings as a bot that answers when spoken to, says it is an AI, and returns the outcome, decisions, action items and transcript.
      14
      2
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives AI agents hands to make phone calls, send messages, and handle CRM/task workflows. It runs with a simulated provider for zero-cost testing and can switch to real providers like Twilio and ElevenLabs.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Let your AI agent call your phone and talk to you — MCP servers for live, interruptible voice calls + tiered alerts, using free self-hosted pieces (pjsua2 + whisper.cpp + Linphone). No paid telephony, no extra API key.
      3
      28
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Gives AI agents phone numbers, email, SMS, and voice calls as MCP tools, enabling them to provision numbers, capture 2FA codes, send messages, and make calls.
      15
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Self-hosted email for AI agents: unlimited mailboxes on your own domain with docker compose, OTP/link extraction, mail_wait_for, web dashboard. v0.7.3: webhook wake example, reliable long waits (mail_wait_for), optional pending journal for task claims. Release: https://github.com/openagentemail/openagentemail/releases/tag/v0.7.3
      25
      55
      Apache 2.0

    TDQS

    A3.9/5.0

    Scored across 38 tools

    Disambiguation4/5

    Most tools target a clearly distinct resource and action, and the detailed descriptions help separate calls, SMS, email, numbers, agents, and verification. A few overlaps remain, especially get_email_events versus get_events narrowed to an email, and lookup_contact versus list_contacts with a query filter.

    Naming Consistency4/5

    The set is overwhelmingly snake_case with predictable verb_noun naming such as list_calls, send_email, get_agent, and route_number. The main deviations are whoami, which does not follow the pattern, and some domain-specific verbs like quote_numbers and lookup_contact.

    Tool Count2/5

    The surface is broad, covering telephony, SMS, email, agents, numbers, contacts, and verifications, but 38 tools is heavy for a single MCP server. A set this large increases selection burden and could reasonably be split by domain.

    Completeness4/5

    Core lifecycle coverage is strong: calls, SMS, email, numbers, agents, and carrier verifications all have create/read/list/update or state-management operations where appropriate. Minor gaps exist, such as no update/delete contact tools and only listing email domains rather than managing them through the MCP surface.

    Maintenance

    ActivityActive
    ResponsivenessSyncing