notify_me_mcp
The notify_me_mcp server enables AI agents and LLMs to send rich notifications to Discord and Slack webhooks with robust security and handling.
Core Features:
Send Notifications: Dispatch plain text or rich formatted messages (Discord embeds, Slack blocks/attachments) to Discord, Slack, or both platforms simultaneously
Test Webhooks: Validate webhook connectivity by sending test messages to configured services
List Services: Retrieve configured webhook services and identify auto-detected defaults
Multi-service Support: Target specific services or all configured platforms with automatic service detection
Advanced Capabilities:
Customization Options: Override display usernames, avatar/icon URLs, and enable text-to-speech (TTS) for Discord
Rate Limit Handling: Automatic retry with exponential backoff for HTTP 429 responses
Security: Webhook URLs never exposed in logs, with comprehensive input validation and schema enforcement
Intelligent Defaults: Automatically chooses available services when unspecified, falling back to Discord if both are configured
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@notify_me_mcp send a Discord notification: 'Build completed successfully'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
notify_me_mcp
TypeScript MCP server for sending notifications to Discord and/or Slack webhooks
A powerful Model Context Protocol (MCP) server that provides webhook notification capabilities to AI agents and LLM applications. Send rich notifications to Discord and Slack with automatic service detection, retry logic, and comprehensive security features.
โจ Features
๐ง Three MCP Tools:
send_notification,validate_webhook,list_services๐ฏ Multi-Service Support: Discord, Slack, or both simultaneously
๐ก๏ธ Security First: Webhook URLs never exposed in logs or process lists
๐ฑ Rich Content: Discord embeds and Slack blocks/attachments support
๐ Robust Retry Logic: Handles rate limiting with exponential backoff
โก Service Auto-Detection: Automatically selects available services
๐ Input Validation: Comprehensive schema validation with Zod
๐ Structured Logging: Secure logging with automatic URL redaction
Related MCP server: Discord Webhook MCP
๐ Quick Start
Prerequisites
Node.js โฅ 23.7.0
npm โฅ 10.9.2
Discord and/or Slack webhook URLs
Installation
Clone the repository
git clone https://github.com/thesammykins/notifyme_mcp.git cd notifyme_mcpInstall dependencies
npm installConfigure webhooks
cp .env.example .env # Edit .env and replace webhook placeholdersBuild the project
npm run build
Configuration
Create a .env file with your webhook URLs:
# Discord webhook URL (optional)
DISCORD_WEBHOOK_URL="https://discord.com/api/webhooks/YOUR_ID/YOUR_TOKEN"
# Slack webhook URL (optional)
SLACK_WEBHOOK_URL="https://hooks.slack.com/services/T00/B00/XXXX"
# Optional: Custom .env file location
# NOTIFY_ME_ENV_FILE="/path/to/custom/.env"
# NOTIFY_ME_ENV_DIR="/path/to/directory"Getting Webhook URLs:
Discord:
Go to Server Settings โ Integrations โ Webhooks
Click "Create Webhook" โ Copy webhook URL
Slack:
Create a Slack app at https://api.slack.com/apps
Enable "Incoming Webhooks" โ Add to workspace
Copy the webhook URL
๐ง Usage with MCP Clients
Claude Desktop Configuration
Add to your Claude Desktop claude_desktop_config.json:
{
"mcpServers": {
"notify_me_mcp": {
"command": "node",
"args": ["path/to/notifyme_mcp/dist/index.js"],
"env": {
"DISCORD_WEBHOOK_URL": "your_discord_webhook_url",
"SLACK_WEBHOOK_URL": "your_slack_webhook_url"
}
}
}
}Other MCP Clients
Use the built server at dist/index.js with any MCP-compatible client over stdio transport.
๐ ๏ธ Available Tools
send_notification
Send notifications to Discord and/or Slack webhooks.
Parameters:
message(string, optional): Plain text messageservice(string, optional): "discord", "slack", or "both" (auto-detected if not specified)embed_json(object/array/string, optional): Rich content (Discord embeds, Slack blocks)username(string, optional): Override display usernameavatar_url(string, optional): Override avatar/icon URLtts(boolean, optional): Enable text-to-speech (Discord only)
Examples:
// Simple notification
{"message": "Task completed successfully โ
"}
// Target specific service
{"message": "Deploy finished", "service": "slack", "username": "CI Bot"}
// Discord embed
{
"service": "discord",
"embed_json": {
"title": "Build Status",
"description": "All tests passed",
"color": 65280
}
}
// Slack blocks
{
"service": "slack",
"embed_json": [
{
"type": "section",
"text": {
"type": "mrkdwn",
"text": "*Deploy Complete* ๐\nAll systems operational"
}
}
]
}validate_webhook
Test webhook connectivity by sending a test message.
Parameters:
service(string, optional): "discord", "slack", or "both"message(string, optional): Custom test message
list_services
List configured webhook services and auto-detected default.
No parameters required.
๐๏ธ Service Auto-Detection
The server automatically detects which services to use:
Only Discord configured โ
discordOnly Slack configured โ
slackBoth configured โ
discord(default for backward compatibility)Use
service: "both"โ Send to all configured services
๐ Security Features
Webhook Protection: URLs never appear in logs, errors, or process lists
Secure Logging: Automatic redaction of sensitive information
Input Validation: All inputs validated with Zod schemas
Rate Limiting: Automatic retry on 429 responses with
Retry-AftersupportTemporary Files: Created with restrictive permissions (077)
๐จ Rich Content Support
Discord Embeds
Supports Discord's native embed objects:
{
"title": "Deployment Status",
"description": "Production deployment completed",
"color": 65280,
"fields": [
{"name": "Version", "value": "v1.2.3", "inline": true},
{"name": "Duration", "value": "3m 42s", "inline": true}
],
"timestamp": "2024-01-15T10:30:00.000Z"
}Slack Blocks & Attachments
Supports Slack's block kit and legacy attachments:
// Blocks (recommended)
[
{
"type": "section",
"text": {
"type": "mrkdwn",
"text": "*Deployment Complete* ๐\nVersion v1.2.3 deployed successfully"
}
}
]
// Attachments (legacy)
{
"attachments": [
{
"color": "good",
"title": "โ
Success",
"text": "All tests passed",
"fields": [
{"title": "Environment", "value": "Production", "short": true}
]
}
]
}๐ Common Colors
Status | Discord (decimal) | Slack (hex/keyword) |
Success |
|
|
Error |
|
|
Warning |
|
|
Info |
|
|
๐งช Development
Run in Development Mode
npm run dev # Uses tsx with watch modeBuild
npm run build # Compiles TypeScript to dist/Start Production Server
npm start # Runs compiled JavaScriptTesting
npm test # Run tests once
npm run test:watch # Run tests in watch mode๐ Project Structure
notify_me_mcp/
โโโ src/
โ โโโ index.ts # MCP server entry point
โ โโโ config.ts # Environment loading & service detection
โ โโโ payload.ts # Discord/Slack payload builders
โ โโโ senders.ts # HTTP senders with retry logic
โ โโโ logger.ts # Secure logging with redaction
โ โโโ types.ts # TypeScript interfaces & Zod schemas
โ โโโ utils.ts # Helper functions
โโโ dist/ # Compiled JavaScript
โโโ .env.example # Environment template
โโโ package.json # Node.js configuration
โโโ tsconfig.json # TypeScript configuration
โโโ README.md # This file๐ง Environment Variables
Variable | Description | Example |
| Discord webhook URL |
|
| Slack webhook URL |
|
| Custom .env file path |
|
| Custom .env directory |
|
๐ Troubleshooting
Common Issues
"No webhook URLs configured"
Ensure
.envfile exists with valid webhook URLsCheck environment variable names match exactly
"Discord message exceeds 2000 character limit"
Discord has a 2000 character limit for message content
Use embeds for longer content or split messages
"Invalid JSON in embed_json"
Validate JSON syntax before sending
Use proper escaping for quotes in JSON strings
Connection timeouts
Check network connectivity to Discord/Slack APIs
Verify webhook URLs are correct and active
Debug Mode
For troubleshooting, you can run with verbose logging:
DEBUG=* npm start๐ค Contributing
Fork the repository
Create a feature branch:
git checkout -b feature/my-featureMake your changes
Build and test:
npm run build && npm testCommit your changes:
git commit -am 'Add some feature'Push to the branch:
git push origin feature/my-featureSubmit a pull request
๐ License
This project is licensed under the MIT License - see the LICENSE file for details.
๐ Related Projects
notify_me.sh - The original bash script that inspired this MCP server
Model Context Protocol - Official MCP documentation
Discord Webhooks - Discord webhook documentation
Slack Webhooks - Slack incoming webhook documentation
๐โโ๏ธ Support
Issues: Report bugs and request features on GitHub Issues
Documentation: Check this README and inline code comments
MCP Protocol: Refer to MCP documentation for client setup
Built with โค๏ธ using TypeScript and the Model Context Protocol
Available Tools
3 toolslist_servicesB
List configured webhook services and auto-detected default
Inputs: no named parameters.
send_notificationC
Send a notification to Discord and/or Slack webhooks
Inputs: avatar_url, embed_json, message, service, +2 more.
validate_webhookC
Test webhook connectivity by sending a test message
Inputs: message, service.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogโฆ
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.
Maintenance
Related MCP Connectors
Control your Discord community: send/read messages, manage channels and forums, and handle webhookโฆ
Webhooks for AI agents: send events, manage endpoints, inspect and retry deliveries.
Let your AI agent notify you by email, Slack, Discord, or webhook. One tool: send_notification.
Send email, push, Slack, Discord, Telegram and webhook notifications and manage templates with Ray.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables Claude Code to send notifications to Discord channels via webhooks when tasks complete, errors occur, or user intervention is needed. Deployed serverlessly on Cloudflare Workers with support for rich message formatting and embeds.8MIT
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to send messages and rich embeds to Discord via webhooks, supporting plain text messages, formatted embeds with images and fields, and customizable webhook appearance for AI-powered Discord notifications and integrations.16 npmMIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables AI models to send plain text messages, formatted release announcements, and teaser previews to Discord channels using webhooks. It provides secure local webhook management and supports rich embeds with customizable styles for automated notifications.141 npm-
- AlicenseNot gradedqualityCmaintenanceUnified notification MCP server with 36 tools to send messages across 23 channels โ Email, SMS, Slack, Telegram, Discord, Teams, WhatsApp, Firebase Push, and more.9MIT