Skip to main content
Glama
HellioSolutions

Hellio Messaging MCP server

Official
by HellioSolutions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Hellio Messaging MCP server

No user-submitted related servers found.

    Related Servers

    • infobip-mcp

      Steph-ux
      A
      license
      Not graded
      quality
      C
      maintenance
      Unified Model Context Protocol (MCP) server for Infobip APIs. Consolidates SMS, WhatsApp, Email, 2FA/OTP, and Account management into a single, high-performance local MCP server.
      1
      MIT

    • Evolution API MCP Server

      serversmx
      A
      license
      B
      quality
      C
      maintenance
      Exposes the Evolution API v2 (WhatsApp) as 121 tools for MCP clients, enabling management of instances, messages, chats, groups, profiles, labels, webhooks, and integrations.
      64
      21 npm
      MIT
    • EZTexting MCP Server by eztexting

      EZTexting MCP Serverofficial

      eztexting
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides MCP tools for SMS messaging, contact management, workflows automation, and account administration through EZTexting's API, supporting both remote Streamable HTTP and local stdio bridge.
      57 npm
      MIT

    • MyOTPApp

      brntech
      A
      license
      Not graded
      quality
      B
      maintenance
      Send and verify one-time passcodes over SMS, WhatsApp and Telegram from any MCP client. Ten tools: send, verify, extend, delivery status, account, usage report, and agent account creation with credit top-ups over a 402. Hosted endpoint or run locally.
      1
      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 28 tools

    Disambiguation5/5

    Each tool targets a distinct operation (send, list, create, etc.) on a specific resource (SMS, voice, OTP, webhook, USSD, etc.). The verb+noun pattern combined with resource-specific prefixes makes it easy to distinguish even related tools like send_sms, send_voice, and send_otp.

    Naming Consistency5/5

    All tools follow the consistent pattern 'hellio_<verb>_<noun>' using snake_case. Verbs are standard (get, list, create, update, delete, send, verify, etc.) and nouns correspond to API resources. No mixing of conventions.

    Tool Count4/5

    With 28 tools, the server covers a broad range of messaging functionalities. While it is on the higher end, the tools are logically grouped (SMS, voice, OTP, USSD, etc.) and each serves a clear purpose, so the count feels justified rather than excessive.

    Completeness4/5

    The tool surface covers the main messaging cycles (send, get, list) for SMS, voice, OTP, email verification, number lookup, and USSD. However, there is no tool to delete or update a webhook, and campaign management lacks a delete/update tool, which are minor gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources