Message MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_URL | No | API endpoint URL | |
| SMTP_HOST | No | SMTP server host | |
| SMTP_PASS | No | SMTP password | |
| SMTP_PORT | No | SMTP server port | |
| SMTP_USER | No | SMTP username | |
| API_METHOD | No | HTTP method for API requests (POST, PUT, PATCH) | |
| NTFY_TOPIC | No | Notification topic for ntfy app | |
| API_HEADERS | No | API headers in JSON string | |
| SMTP_SECURE | No | Use secure connection for SMTP (true/false) |
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 |
|---|---|
| notifyA | Send notifications and messages through multiple channels (desktop, email, API). Use this tool to notify users about any important information, progress updates, task completions, alerts, or any other communication needs. |
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 no possibility of confusion or overlap.
Single tool uses a clear, verb-based name 'notify' which is consistent with its purpose.
One tool for a notification domain is too few; typically multiple operations (e.g., send, schedule, manage templates) are needed.
The tool sends notifications but lacks capabilities for managing channels, templates, logs, or preferences, leaving significant gaps.