MCP.so
Sign In

MCP Server Notifier

@tuberrabbit

Basic information

Category

Developer Tools

License

MIT

Transports

stdio

Author

tuberrabbit

About MCP Server Notifier

Lightweight Node.js server sending webhook notifications. Ideal for devs using AI agents (e.g., Cursor) on multi-projects, alerting task completion for efficient switching. Features webhook alerts, multi-project dev, AI integration, easy setup for dev tools & automation.

MCP Server Notifier config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "mcp-server-notifier": {
      "command": "docker",
      "args": [
        "pull",
        "zudsniper/mcp-server-notifier:latest"
      ]
    }
  }
}

MCP Server Notifier tools

1

Send rich notifications to any configured webhook

Overview

What is MCP Server Notifier?

A lightweight notification service that integrates with MCP (Model Context Protocol) to send webhooks when AI agents complete tasks. It supports multiple webhook providers and customizable messages.

How to use MCP Server Notifier?

Install globally via npm (npm install -g mcp-server-notifier), Docker (docker pull zudsniper/mcp-server-notifier), or from source. Configure with environment variables WEBHOOK_URL and WEBHOOK_TYPE, then invoke via MCP client or Cursor integration. The server exposes a notify tool for sending rich notifications.

Key features of MCP Server Notifier

  • Send webhook notifications when AI agents finish tasks.
  • Supports Discord, Slack, Microsoft Teams, Feishu, Ntfy, and generic JSON.
  • Include images in notifications via Imgur integration.
  • Multi-project management with separate webhook configurations.
  • Customizable messages with title, body, link, and attachments.
  • Template support for ntfy (status, question, progress, problem).

Use cases of MCP Server Notifier

  • Alerting a team when a long-running data processing task completes.
  • Sending progress updates for automated build or backup jobs.
  • Reporting errors or critical issues from an AI agent to a chat channel.
  • Notifying a user about a question that requires human input.
  • Tracking status of multiple projects through a single notification server.

Frequently asked questions

1

Which webhook types are supported?

Discord, Slack, Microsoft Teams, Feishu, Ntfy, and Generic JSON (via `WEBHOOK_TYPE`).

2

How do I use authentication tokens?

Set `WEBHOOK_TOKEN` for ntfy webhooks only; it is sent as a Bearer token in the `Authorization` header. Basic authentication is not supported, and the token is ignored by other providers.

3

Can I include images in notifications?

Yes. Use the optional `image` parameter with a local file path to upload to Imgur, or provide an `imageUrl` for an external image. Imgur upload requires a `clientId` in the configuration.

4

What parameters does the `notify` tool accept?

`message` (required), plus optional `title`, `link`, `imageUrl`, `image`, `priority` (ntfy only, 1-5), `attachments` (ntfy only), `template`, `templateData`, and `actions` (ntfy only).

5

Are templates fully supported?

Templates (status, question, progress, problem) are currently under development with limited support. They work best with ntfy.sh but may not be fully implemented for all webhook providers.

Comments

More Developer Tools MCP servers