Skip to main content
Glama
DevEngageLab

engagelab-sms-mcp

by DevEngageLab

Related Servers

Alternatives to engagelab-sms-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to send SMS and manage messaging workflows through ClickSend, including pricing estimates, contact lists, templates, history, and statistics.
      6
      49 npm
      3
      MIT
    • A
      license
      C
      quality
      D
      maintenance
      Enables AI agents to send, receive, schedule, and manage SMS and MMS messages using the Twilio Programmable Messaging API. It provides comprehensive tools for handling bulk messaging, conversation threads, and real-time inbox monitoring through a secure, production-grade architecture.
      16
      1
      MIT
    • 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
      13 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to send SMS, manage contacts, verify numbers, and query campaigns via SMS Masivos platform using natural language.
      30
      9 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables sending SMS messages, managing contacts, campaigns, and inbox from AI assistants like Claude and ClickUp.
      33 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI-powered SMS messaging through Twilio with automatic conversation threading, message status tracking, and webhook support for receiving inbound messages.
      45 npm
      1
      MIT

    TDQS

    A3.8/5.0

    Scored across 1 tool

    Disambiguation5/5

    Only one tool exists, so there is no possibility of ambiguity between tools. Every tool has a clearly distinct purpose by virtue of being the only tool.

    Naming Consistency5/5

    The single tool name follows a clear verb_noun pattern (send_sms), which is consistent and predictable. With only one tool, naming consistency is trivially maintained.

    Tool Count3/5

    With just one tool, the server feels thin for an SMS integration, as typical SMS APIs offer more functionality like status checks or template management. However, for a focused send-only use case, it may be appropriate.

    Completeness2/5

    The tool surface is limited to sending SMS, leaving obvious gaps such as checking delivery status, managing templates, or retrieving message history. Agents cannot perform these operations, which may cause failures for common SMS workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues