MCP Server Notifier

You can use the MCP Server Notifier to receive webhook alerts whenever your AI agents complete tasks. It supports multiple webhook providers, image attachments, and multi-project setups, making it easy to stay informed about progress and results across your MCP ecosystem.

How to use

Set up the notifier as part of your MCP workflow so that your AI agents automatically push updates to your preferred webhook service. You can configure it in Cursor, or run it directly using a local MCP server command. The notifier forwards task completion events as rich notifications, which can include titles, bodies, links, and images.

Key usage patterns you can implement include: - Trigger a notification when a task finishes, with a summary and a link to details. - Route messages to different webhook providers depending on project or task type. - Attach an image to notifications to visually summarize results.

To customize behavior, you can specify the webhook destination, the type of webhook, and optional authentication. You can also extend notifications with titles, links, images, and structured templates when supported by the chosen provider.

How to install

Prerequisites: you need Node.js and npm installed to install and build the notifier. If you prefer containerized usage, Docker is supported as well.

Install via npm (global):

npm install -g mcp-server-notifier

Install via Docker (pull and run):

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-notifier

Install from source (clone, install, build):

git clone https://github.com/zudsniper/mcp-server-notifier.git
cd mcp-server-notifier
npm install
npm run build

Configuration and usage notes

By default, the notifier supports several webhook types: Discord, Slack, Microsoft Teams, Feishu, Ntfy, and a Generic JSON option. You can set the webhook type and URL through environment variables when you run the notifier.

Optional authentication is available via WEBHOOK_TOKEN for ntfy webhook requests. If WEBHOOK_TOKEN is provided, it is sent as a Bearer token in the Authorization header only for ntfy requests. Other webhook providers ignore this token.

For advanced setups, you can supply a webhook-config.json file with specific provider settings and an optional Imgur client ID for image uploads.

Cursor integration example

If you use Cursor, you can register the notifier as a global MCP server and pass the required command and environment variables.

{
  "mcpServers": {
    "notifier": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-notifier"
      ],
      "env": {
        "WEBHOOK_URL": "https://ntfy.sh/webhook-url-example",
        "WEBHOOK_TYPE": "ntfy"
      }
    }
  }
}

Usage tips

• The notifier can be used to push rich notifications to supported webhook providers. - You can tailor the notification content with a title, body, and link for quick access to details. - When using ntfy, templates and additional fields may be available to structure progress, status, or problem messages.

Available tools

notify

Send rich notifications to any configured webhook with optional title, link, image, and template data. This tool is the core action used to emit events from MCP tasks.