Lightweight Node.js server for sending webhook notifications. Supports Discord, Slack, Teams, Feishu, and custom webhooks. Ideal for AI-assisted
If you already use Notifier, the notifier mcp server is the piece that lets your assistant work with it directly. Lightweight Node.js server for sending webhook notifications. Supports Discord, Slack, Teams, Feishu, and custom webhooks. Ideal for AI-assisted developers working across multiple projects.
A lightweight notification service that integrates with MCP (Model Context Protocol) to send webhooks when AI agents complete tasks.
mcp-server-notifier on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Purpose — Send rich notifications to any configured webhookInput — - message - Text content of the notificationConfiguration is passed through the environment: WEBHOOK_URL, WEBHOOK_TYPE, WEBHOOK_TOKEN, DOCKERHUB_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Notifier's toolset — Purpose, Input — is a fair guide to whether it matches your workflow. It is maintained by tuberrabbit; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Purpose | Send rich notifications to any configured webhook |
| Input | - message - Text content of the notification |
{
"mcpServers": {
"server-notifier": {
"command": "npx",
"args": ["-y", "mcp-server-notifier"],
"env": {
"WEBHOOK_URL": "your-value",
"WEBHOOK_TYPE": "your-value",
"WEBHOOK_TOKEN": "your-value",
"DOCKERHUB_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| WEBHOOK_URL | Endpoint or connection string the server talks to. | Yes |
| WEBHOOK_TYPE | Configuration value read at startup. | Optional |
| WEBHOOK_TOKEN | Credential the server authenticates with. | Yes |
| DOCKERHUB_TOKEN | Credential the server authenticates with. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.