Skip to main content
Glama
engagelab-sms-mcp

engagelab-sms-mcp

by DevEngageLab

engagelab-sms-mcp

An MCP server that lets AI assistants send SMS messages through EngageLab.

Add it to your MCP client (Cursor, Claude Desktop, etc.) and the AI can send template-based SMS on your behalf.

Prerequisites

  • Node.js 18+

  • An EngageLab account with SMS API credentials (dev_key and dev_secret)

  • At least one approved SMS template in your EngageLab console

Related MCP server: Twilio SMS Server

Quick Start

Cursor

Go to Settings > MCP, click Add new MCP server, and paste:

{
  "mcpServers": {
    "engagelab-sms": {
      "command": "npx",
      "args": ["-y", "engagelab-sms-mcp"],
      "env": {
        "ENGAGELAB_DEV_KEY": "<your_dev_key>",
        "ENGAGELAB_DEV_SECRET": "<your_dev_secret>"
      }
    }
  }
}

Claude Desktop

Open Settings > Developer > Edit Config and add to mcpServers:

{
  "mcpServers": {
    "engagelab-sms": {
      "command": "npx",
      "args": ["-y", "engagelab-sms-mcp"],
      "env": {
        "ENGAGELAB_DEV_KEY": "<your_dev_key>",
        "ENGAGELAB_DEV_SECRET": "<your_dev_secret>"
      }
    }
  }
}

Other MCP Clients

Any MCP client that supports stdio transport can use this server. Point the command to npx -y engagelab-sms-mcp and pass the two required environment variables.

Available Tools

send_sms

Send SMS messages through EngageLab using a pre-approved template.

Input:

Field

Type

Required

Description

to

string[]

Yes

Target phone numbers (international format recommended, e.g. +8618700001111)

template.id

string

Yes

Approved EngageLab SMS template ID

template.params

object

Yes

Template variable values, e.g. {"code": "123456"}

Example input:

{
  "to": ["+8618700001111"],
  "template": {
    "id": "your-template-id",
    "params": {
      "code": "123456"
    }
  }
}

Output:

Field

Type

Description

success

boolean

Whether the request was accepted

plan_id

string

EngageLab plan ID for tracking

total_count

number

Total recipients submitted

accepted_count

number

Recipients accepted for delivery

message_id

string

Message identifier (if available)

message

string

Status or error description

code

number

EngageLab response code (0 = success)

Environment Variables

Variable

Required

Default

Description

ENGAGELAB_DEV_KEY

Yes

—

Your EngageLab dev key

ENGAGELAB_DEV_SECRET

Yes

—

Your EngageLab dev secret

ENGAGELAB_BASE_URL

No

https://smsapi.engagelab.com

API base URL

ENGAGELAB_REQUEST_TIMEOUT_MS

No

10000

Request timeout in milliseconds

ENGAGELAB_MAX_RETRIES

No

1

Max retry attempts for transient failures

Troubleshooting

Server fails to start with "Missing required environment variable"

  • Make sure both ENGAGELAB_DEV_KEY and ENGAGELAB_DEV_SECRET are set in the env block of your MCP client config.

send_sms returns error code 3002 ("invalid template id format")

  • Check that your template ID matches an approved template in the EngageLab console.

send_sms returns error code related to template params

  • Verify that template.params keys match the variable names defined in your EngageLab template.

SMS not received

  • Use international phone number format (e.g. +8618700001111).

  • Confirm the template is approved and not suspended.

License

MIT

Available Tools

1 tool
send_smsSend SMSA

Send SMS through EngageLab using a template. Requires ENGAGELAB_DEV_KEY and ENGAGELAB_DEV_SECRET environment variables.

Inputs: to (required), template (required). Returns: code, message, plan_id, success, +3 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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 recent community issues

    Related MCP Connectors

    Related MCP Servers

    • 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.
      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
      19 npm
      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
      A
      quality
      D
      maintenance
      Enables AI assistants to send SMS, manage contacts, verify numbers, and query campaigns via SMS Masivos platform using natural language.
      30
      57 npm
      MIT