What can you do with this server?

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

Which integrations are available for this server?

Enables sending rich notifications to Discord channels via webhooks, supporting embeds, custom usernames, avatars, and text-to-speech messages Allows sending notifications to Slack channels through webhooks, supporting rich formatting with blocks, attachments, and custom display options

How do I use notify_me_mcp?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. 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

by thesammykins

Overview Schema Source Related Servers Score Discussions Admin

TypeScript

Hybrid

notify_me_mcp

TypeScript MCP server for sending notifications to Discord and/or Slack webhooks

License: MIT Node.js Version TypeScript

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_mcp

Install dependencies
```
npm install
```

Configure webhooks

cp .env.example .env
# Edit .env and replace webhook placeholders

Build 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 message
service (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 username
avatar_url (string, optional): Override avatar/icon URL
tts (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 → discord
Only Slack configured → slack
Both 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-After support
Temporary 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	`65280`	`#36a64f` or `good`
Error	`16711680`	`#ff0000` or `danger`
Warning	`16753920`	`#ffa500` or `warning`
Info	`3447003`	`#3498db`

🧪 Development

Run in Development Mode

npm run dev  # Uses tsx with watch mode

Build

npm run build  # Compiles TypeScript to dist/

Start Production Server

npm start  # Runs compiled JavaScript

Testing

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`	Discord webhook URL	`https://discord.com/api/webhooks/...`
`SLACK_WEBHOOK_URL`	Slack webhook URL	`https://hooks.slack.com/services/...`
`NOTIFY_ME_ENV_FILE`	Custom .env file path	`/path/to/.env`
`NOTIFY_ME_ENV_DIR`	Custom .env directory	`/path/to/config`

🐛 Troubleshooting

Common Issues

"No webhook URLs configured"

Ensure .env file exists with valid webhook URLs
Check 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-feature
Make your changes
Build and test: npm run build && npm test
Commit your changes: git commit -am 'Add some feature'
Push to the branch: git push origin feature/my-feature
Submit a pull request

📄 License

This project is licensed under the MIT License - see the LICENSE file for details.

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 tools

list_servicesB

List configured webhook services and auto-detected default

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

B3.2/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It mentions listing both configured and auto-detected services, which adds some behavioral context, but doesn't disclose critical details like whether this is a read-only operation, potential rate limits, authentication needs, or what the output format looks like. For a tool with zero annotation coverage, this is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's function without any wasted words. It's front-loaded and appropriately sized for its simple purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no annotations, no output schema), the description is adequate but has gaps. It explains what is listed but doesn't cover behavioral aspects like safety or output format. For a list operation, more context on what 'configured' and 'auto-detected' entail would improve completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate, but since there are no parameters, the baseline is high. It could be a 5 if it explicitly stated 'no parameters required', but it's still very clear in context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'List' and the resource 'configured webhook services and auto-detected default', making the purpose understandable. However, it doesn't explicitly distinguish this tool from its siblings (send_notification, validate_webhook), which are clearly different operations, so it doesn't reach the highest score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context for listing services, or compare it to sibling tools like send_notification or validate_webhook, leaving usage decisions to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

send_notificationC

Send a notification to Discord and/or Slack webhooks

ParametersJSON Schema

Name	Required	Description	Default
`avatar_url`	No
`embed_json`	No
`message`	No
`service`	No
`tts`	No
`username`	No

TDQS

C2.5/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the basic action without mentioning critical traits like required webhook setup, authentication needs, rate limits, error handling, or what happens on failure. This is inadequate for a tool that likely involves external API calls and potential side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose without any fluff. It's appropriately sized and front-loaded, making it easy to grasp immediately, which is ideal for conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of sending notifications to external services, no annotations, no output schema, and 0% schema coverage, the description is severely incomplete. It lacks essential details like prerequisites (e.g., webhook URLs), behavioral expectations, and error handling, making it inadequate for safe and effective use by an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage for 6 parameters, the description adds no meaning beyond the schema. It doesn't explain what parameters like 'avatar_url', 'embed_json', or 'tts' do, how they interact, or provide examples. The description fails to compensate for the lack of schema documentation, leaving parameters largely unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('send a notification') and target destinations ('Discord and/or Slack webhooks'), which is specific and actionable. However, it doesn't distinguish this tool from its siblings (list_services, validate_webhook), which are clearly different operations, so it doesn't reach the highest score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, such as whether it's for urgent alerts or general messaging, or how it relates to sibling tools like validate_webhook. It mentions multiple services but doesn't clarify when to choose one over another, leaving usage context implied at best.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

validate_webhookC

Test webhook connectivity by sending a test message

ParametersJSON Schema

Name	Required	Description	Default
`message`	No
`service`	No

TDQS

C2.8/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions sending a test message but lacks critical details: whether this is a read-only or destructive operation (e.g., could it trigger unintended actions?), authentication requirements, rate limits, or what the response looks like (e.g., success/failure indicators). For a tool with potential side effects, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core purpose without unnecessary words. Every part earns its place by specifying the action and resource, making it easy to scan and understand quickly. No redundancy or fluff is present.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (2 parameters, no annotations, no output schema), the description is incomplete. It lacks parameter explanations, behavioral context (e.g., side effects), and output details. While conciseness is high, it sacrifices necessary information for a tool that interacts with external services, leaving the agent under-informed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for undocumented parameters. It doesn't explain the two parameters ('message' and 'service') at all—no mention of what the message should contain, the purpose of the service parameter, or the enum values ('discord', 'slack', 'both'). The description adds no value beyond the bare schema, failing to address the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb ('Test') and resource ('webhook connectivity'), and specifies the action ('by sending a test message'). It distinguishes itself from sibling tools like 'list_services' and 'send_notification' by focusing on validation rather than listing or general notification sending. However, it doesn't explicitly differentiate from potential alternatives for webhook testing within the same domain.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., webhook setup), when-not-to-use scenarios (e.g., for production notifications), or explicit alternatives among the sibling tools. The agent must infer usage from the purpose alone, which is insufficient for optimal tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

3 tool updatesv1.0.0Aug 15, 2025
- First observedlist_services
- First observedsend_notification
- First observedvalidate_webhook

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.2/5.0

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count4/5

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.

Completeness4/5

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

ActivityInactive

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

sachicali-discordmcp-suiteOAuth
ai.smithery
Control your Discord community: send/read messages, manage channels and forums, and handle webhook…
Communication Social Media
2
AgentPing
io.github.Noriget
Let your AI agent notify you by email, Slack, Discord, or webhook. One tool: send_notification.
Communication Email
2
webhook.coOAuth
co.webhook
Receive, inspect, replay and deliver webhooks — with signature verification and agent triggers.
App Automation API Testing
2
webhook-relay A
com.agishub
Fire-and-forget webhooks for agents with guaranteed, retried delivery and status polling. x402
App Automation Agent Orchestration
211

Related MCP Servers

Discord Notification MCP
Communication Cloud Platforms
kstonekuan
A
license
Not graded
quality
D
maintenance
Enables 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.
Updated a year ago (2025-06-23 17:04 UTC)
8
MIT
Discord Webhook MCP
Communication App Automation
LLMTooling
A
license
Not graded
quality
D
maintenance
Enables 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.
Updated 9 months ago (2025-12-09 00:52 UTC)
13
MIT
Discord MCP Server
Communication App Automation Developer Tools
MoshPitLabs
F
license
Not graded
quality
Not graded
maintenance
Enables 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.
Updated 7 months ago (2026-01-31 14:12 UTC)
107
-
notify-hub
Communication App Automation
GabrielBBaldez
A
license
Not graded
quality
C
maintenance
Unified notification MCP server with 36 tools to send messages across 23 channels — Email, SMS, Slack, Telegram, Discord, Teams, WhatsApp, Firebase Push, and more.
Updated 6 months ago (2026-03-23 17:41 UTC)
5
MIT

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/thesammykins/notifyme_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

notify_me_mcp

✨ Features

🚀 Quick Start

Prerequisites

Installation

Configuration

🔧 Usage with MCP Clients

Claude Desktop Configuration

Other MCP Clients

🛠️ Available Tools

send_notification

validate_webhook

list_services

🏗️ Service Auto-Detection

🔒 Security Features

🎨 Rich Content Support

Discord Embeds

Slack Blocks & Attachments

📊 Common Colors

🧪 Development

Run in Development Mode

Build

Start Production Server

Testing

📁 Project Structure

🔧 Environment Variables

🐛 Troubleshooting

Common Issues

Debug Mode

🤝 Contributing

📄 License

🔗 Related Projects

🙋‍♂️ Support

Available Tools

Tool Schema Changelog

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

`send_notification`

`validate_webhook`

`list_services`