notify_me_mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOTIFY_ME_ENV_DIR | No | Custom .env directory | |
| SLACK_WEBHOOK_URL | No | Slack webhook URL (optional) | |
| NOTIFY_ME_ENV_FILE | No | Custom .env file path | |
| DISCORD_WEBHOOK_URL | No | Discord webhook URL (optional) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_servicesB | List configured webhook services and auto-detected default |
| validate_webhookC | Test webhook connectivity by sending a test message |
| send_notificationC | Send a notification to Discord and/or Slack webhooks |
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 3 tools
Each tool has a clearly distinct purpose with no overlap: list_services is for configuration listing, send_notification is for actual notifications, and validate_webhook is for testing connectivity. An agent can easily differentiate these functions.
All tools follow a consistent verb_noun pattern with snake_case: list_services, send_notification, and validate_webhook. The naming is predictable and readable throughout.
With 3 tools, the count is reasonable for a notification server, covering core operations. It might feel slightly thin if advanced features like service management are needed, but it's well-scoped for basic functionality.
The tools cover key notification workflows: listing services, sending notifications, and validating webhooks. Minor gaps exist, such as no explicit tool for creating or deleting webhook configurations, but agents can likely work around this for basic use cases.