mcp-server-notifier
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., "@mcp-server-notifier notify me on Discord when the task is finished"
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.
MCP Server Notifier
A lightweight notification service that integrates with MCP (Model Context Protocol) to send webhooks when AI agents complete tasks.

Authors
Originally created by tuberrabbit@gmail.com.
Currently maintained by zudsniper.
Related MCP server: AgentPing
Features
Webhook Notifications: Receive alerts when your AI agents complete tasks
Multiple Webhook Providers: Support for Discord, Slack, Microsoft Teams, Feishu, Ntfy, and custom webhooks
Image Support: Include images in notifications via Imgur
Multi-Project Support: Efficiently manage notifications across different projects
Easy Integration: Simple setup with AI tools like Cursor
Customizable Messages: Send personalized notifications with title, body, and links
Installation
Option 1: Using npm
npm install -g mcp-server-notifierOption 2: Using Docker
docker pull zudsniper/mcp-server-notifier:latest
# Run with environment variables
docker run -e WEBHOOK_URL=https://your-webhook-url -e WEBHOOK_TYPE=discord zudsniper/mcp-server-notifierOption 3: From Source
git clone https://github.com/zudsniper/mcp-server-notifier.git
cd mcp-server-notifier
npm install
npm run buildIntegration
Cursor Integration
Go to your 'Cursor Settings'
Click
MCPin the sidebar, then click+ Add new global MCP serverAdd
mcp-server-notifier.
{
"mcpServers": {
"notifier": {
"command": "npx",
"args": [
"-y",
"mcp-server-notifier"
],
"env": {
"WEBHOOK_URL": "https://ntfy.sh/webhook-url-example",
"WEBHOOK_TYPE": "ntfy"
}
}
}
}
Configuration
By default, the notifier supports several webhook types:
Discord
Slack
Microsoft Teams
Feishu
Ntfy
Generic JSON
You can specify the webhook type and URL through environment variables:
env WEBHOOK_URL="https://your-webhook-url" WEBHOOK_TYPE="discord" npx -y mcp-server-notifierAuthentication Tokens
WEBHOOK_TOKEN is an optional environment variable. When set, it will be included as a Bearer token in the Authorization header only for ntfy webhook requests. If WEBHOOK_TOKEN is not set, no Authorization header is sent.
Basic Authentication is not supported.
This token is ignored by all other webhook providers (Discord, Slack, Teams, Feishu, Generic JSON).
Example:
env WEBHOOK_URL="https://ntfy.sh/your-topic" WEBHOOK_TYPE="ntfy" WEBHOOK_TOKEN="your-secret-token" npx -y mcp-server-notifierConfiguration File
For more advanced configuration, you can create a webhook-config.json file:
{
"webhook": {
"type": "discord",
"url": "https://discord.com/api/webhooks/your-webhook-url",
"name": "My Notifier"
},
"imgur": {
"clientId": "your-imgur-client-id"
}
}See the Configuration Guide for full details and examples.
Usage
Ask your AI agent to notify you with a custom message when a task is complete
Configure it as a persistent rule in Cursor settings to avoid repeating the setup
For detailed usage instructions, see the Usage Guide.
Available Tools
notifyPurpose: Send rich notifications to any configured webhook
Input:
message- Text content of the notificationtitle(optional) - Title for the notificationlink(optional) - URL to include in the notification (used as click action for ntfy)imageUrl(optional) - URL of an image to include (legacy, useimageorattachments)image(optional) - Local file path of an image to upload to Imgurpriority(optional, ntfy only) - Notification priority (1-5)attachments(optional, ntfy only) - Array of URLs to attachtemplate(optional, ntfy only) - Predefined template to use: status, question, progress, problemtemplateData(optional, ntfy only) - Data to populate the chosen templateactions(optional, ntfy only) - Array of action button definitions (vieworhttp)
Best for: General notification needs
Note: Template functionality is currently under development and has limited support. Templates work best with ntfy.sh but may not be fully implemented for all webhook providers. See the ROADMAP.md file for future implementation plans.
NTFY Templates
When using ntfy.sh as your webhook provider, you can use the following predefined templates:
Status Template (
status)Purpose: Send status updates about systems, processes, or tasks
Data Fields:
status- Current status (e.g., "online", "completed", "pending")details(optional) - Additional information about the statustimestamp(optional) - When this status was recordedcomponent(optional) - The system component this status applies to
Question Template (
question)Purpose: Ask questions that require a response
Data Fields:
question- The main question being askedcontext(optional) - Background information for the questionoptions(optional) - Possible answer optionsdeadline(optional) - When a response is needed by
Progress Template (
progress)Purpose: Track progress of long-running tasks
Data Fields:
title- Name of the task or processcurrent- Current progress valuetotal- Total value to reach completionpercentage(optional) - Explicit percentage value (calculated if not provided)eta(optional) - Estimated time to completiondetails(optional) - Additional information about the progress
Problem Template (
problem)Purpose: Report errors or issues
Data Fields:
title- Short description of the problemdescription(optional) - Detailed information about the problemseverity(optional) - How severe the problem is (e.g., "critical", "warning")source(optional) - Where the problem originatedtimestamp(optional) - When the problem occurredsolution(optional) - Suggested ways to fix the problem
Example Using Template:
// Send a progress notification
{
"template": "progress",
"templateData": {
"title": "Database Backup",
"current": 75,
"total": 100,
"eta": "2 minutes remaining",
"details": "Compressing backup files"
},
"priority": 3
}Docker Support
The MCP Server Notifier is available as a Docker image:
docker pull zudsniper/mcp-server-notifier:latestRun with environment variables:
docker run -e WEBHOOK_URL=https://your-webhook-url -e WEBHOOK_TYPE=discord zudsniper/mcp-server-notifierExample Configurations
Example webhook configurations are available in the examples directory.
Development
Setting Up Development Environment
Clone the repository:
git clone https://github.com/zudsniper/mcp-server-notifier.git
cd mcp-server-notifierInstall dependencies:
npm installBuild the project:
npm run buildTesting Your Changes
Run the MCP server in development mode:
# Install the MCP Inspector if you haven't already
npm install -g @modelcontextprotocol/inspector
# Start the server with the Inspector
npx @modelcontextprotocol/inspector node build/index.jsThe Inspector provides a web interface where you can:
Send requests to your tools
View request/response logs
Debug issues with your implementation
Releasing New Versions
To release a new version:
Update version in
package.jsonPush changes to the
releasebranchGitHub Actions will automatically:
Run tests
Build and push Docker images
Publish to npm
Create a GitHub Release
Required repository secrets for CI/CD:
DOCKERHUB_USERNAME- Docker Hub usernameDOCKERHUB_TOKEN- Docker Hub access tokenNPM_TOKEN- npm access token
License
MIT License - see LICENSE file for details.
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
This MCP is certified by MCP Review.
Certification page: https://mcpreview.com/mcp-servers/tuberrabbit/mcp-server-notifier
Available Tools
1 toolnotifyB
Send a notification to configured webhook services (Discord, Slack, Teams, Feishu, ntfy, custom)
Inputs: message (required), title, link, imageUrl, +4 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Let your AI agent notify you by email, Slack, Discord, or webhook. One tool: send_notification.
Push notifications for AI agents - send instant iPhone notifications from any MCP client.
Send yourself a push notification from an AI assistant. No account, one environment variable.
Let your AI agents ask you for decisions and get your answers back, from your phone or the web.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables sending real-time and webhook notifications when AI agents complete tasks, with support for Discord, Slack, Teams, Feishu, Ntfy, and custom webhooks.6MIT
- AlicenseNot gradedqualityDmaintenanceLet your AI agent notify you via email, Slack, Discord, or webhook using a single tool.MIT
- AlicenseBqualityDmaintenanceAn MCP server that lets LLM agents dispatch native OS notifications when a task finishes. It supports cross-platform desktop notifications, task tokens for updates, mobile bridges, and quiet hours.2MIT
- FlicenseNot gradedqualityAmaintenanceA local MCP server that lets AI agents send desktop notifications during tasks, ask for attention, and report completion. Supports macOS, Linux, and Windows, with optional webhook delivery.835-