mcp-server-notifier
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WEBHOOK_URL | Yes | The URL of the webhook endpoint. | |
| WEBHOOK_TYPE | Yes | The type of webhook (e.g., discord, slack, teams, feishu, ntfy, generic). | |
| WEBHOOK_TOKEN | No | Optional token for ntfy webhook authentication (Bearer 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| notifyB | Send a notification to configured webhook services (Discord, Slack, Teams, Feishu, ntfy, custom) |
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.
The single tool name 'notify' is appropriate for its function, and no inconsistencies exist.
One tool for a notification server is slightly minimal but still reasonable for sending notifications to configured webhooks.
The notification tool covers the core sending operation, but lacks tools for managing webhook configurations or testing connectivity, which are notable gaps.