engagelab-sms-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@engagelab-sms-mcp Send SMS with template 'verify_code' to +8613800000000 using params code=123456"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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_keyanddev_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 |
|
| Yes | Target phone numbers (international format recommended, e.g. |
|
| Yes | Approved EngageLab SMS template ID |
|
| Yes | Template variable values, e.g. |
Example input:
{
"to": ["+8618700001111"],
"template": {
"id": "your-template-id",
"params": {
"code": "123456"
}
}
}Output:
Field | Type | Description |
|
| Whether the request was accepted |
|
| EngageLab plan ID for tracking |
|
| Total recipients submitted |
|
| Recipients accepted for delivery |
|
| Message identifier (if available) |
|
| Status or error description |
|
| EngageLab response code ( |
Environment Variables
Variable | Required | Default | Description |
| Yes | — | Your EngageLab dev key |
| Yes | — | Your EngageLab dev secret |
| No |
| API base URL |
| No |
| Request timeout in milliseconds |
| No |
| Max retry attempts for transient failures |
Troubleshooting
Server fails to start with "Missing required environment variable"
Make sure both
ENGAGELAB_DEV_KEYandENGAGELAB_DEV_SECRETare set in theenvblock 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.paramskeys 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.
Links
License
MIT
Available Tools
1 toolsend_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
Scored across 1 tool
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.
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.
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.
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
Related MCP Connectors
Envoyez des SMS et gérez vos campagnes directement depuis vos agents IA.
Send and schedule SMS and WhatsApp messages, manage contacts and templates, and track delivery.
Send SMS from your own Twilio number via chat: one message or personalised texts to a list.
Business texting for AI agents: send texts, read threads, manage contacts and run campaigns.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI-powered SMS messaging through Twilio with automatic conversation threading, message status tracking, and webhook support for receiving inbound messages.1MIT
- AlicenseBqualityDmaintenanceEnables 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.119 npmMIT
- AlicenseCqualityDmaintenanceEnables 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.161MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to send SMS, manage contacts, verify numbers, and query campaigns via SMS Masivos platform using natural language.3057 npmMIT