Skip to main content
Glama
mojawave

MojaWave MCP

Official
by mojawave
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to MojaWave MCP

No user-submitted related servers found.

    Related Servers

    • 46elks MCP Server

      palhamel
      A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants and MCP-compatible clients to send and manage SMS messages through the 46elks API, leveraging Swedish telecommunications infrastructure.
      6
      MIT
    • SendAPI MCP Server by SendAPI-co

      SendAPI MCP Serverofficial

      SendAPI-co
      A
      license
      A
      quality
      D
      maintenance
      Enables any MCP-compatible AI agent to send WhatsApp messages, SMS, OTP codes, and email through a single REST API.
      18
      MIT

    • Twilio SMS Server

      mustafa-boorenie
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to send SMS messages via Twilio through the Model Context Protocol or a standalone REST API. It supports standard messaging, automated greetings, and creative content generation using natural language.
      1
      27 npm
      MIT

    • TopSMS MCP server

      topsms-ghb
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to send and schedule SMS, send bulk messages, verify one-time codes, check delivery status, and retrieve credit from a Czech SMS gateway.
      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.4/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool covers a distinct operation: sending SMS/email (single and bulk), listing resources, checking status, and verifying webhooks. There is no overlap; even the two 'send' tools are clearly differentiated by single vs. bulk, and each 'list' tool targets a specific resource type.

    Naming Consistency4/5

    All tools use a consistent verb_noun pattern in snake_case (get_, list_, send_, verify_). There is a minor inconsistency: 'list_sms_sender_ids' uses 'sender_ids' while the email counterparts use 'senders' (list_email_senders). The deviation is small but slightly breaks the pattern.

    Tool Count5/5

    10 tools is a well-scoped set for a messaging API. It covers essential operations (sending, listing, status, credit, webhook) without being overwhelming. The count falls comfortably within the ideal 3-15 range.

    Completeness3/5

    The server covers basic send, status, and listing operations but lacks several expected capabilities: no bulk email sending, no way to list sent messages or search history, no update/delete for resources like sender IDs or domains, and no cancellation of scheduled messages. These gaps are notable for a full messaging lifecycle.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources