engagelab-sms-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ENGAGELAB_DEV_KEY | Yes | Your EngageLab dev key | |
| ENGAGELAB_BASE_URL | No | API base URL | https://smsapi.engagelab.com |
| ENGAGELAB_DEV_SECRET | Yes | Your EngageLab dev secret | |
| ENGAGELAB_MAX_RETRIES | No | Max retry attempts for transient failures | 1 |
| ENGAGELAB_REQUEST_TIMEOUT_MS | No | Request timeout in milliseconds | 10000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_smsA | Send SMS through EngageLab using a template. Requires ENGAGELAB_DEV_KEY and ENGAGELAB_DEV_SECRET environment variables. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.