smspm-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SMSPM_HASH | Yes | Your SMSPM hash (looks like a UUID) | |
| SMSPM_TOKEN | Yes | Your SMSPM API token |
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_smsB | Send an SMS message via SMSPM. Requires a recipient phone number (international format), message text, and optional sender name. |
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 confusion with other tools.
With a single tool, naming consistency is not applicable; the name 'send_sms' follows a clear verb_noun pattern.
One tool is borderline thin for an SMS service; additional tools like checking delivery status could be expected.
The tool only supports sending SMS without any supporting operations like status checks, scheduling, or contact management, leaving significant gaps.