slack_notify_generalLABSCO SUMMARY
One tool per channel, so the routing cannot be wrong.
Servers that take a channel as a parameter let a model post an outage alert into the general channel by fumbling one string; naming a separate tool per destination makes that a different call rather than a bad argument. The scope is one direction only — this posts, it does not read Slack — and because it runs on webhooks there is no OAuth app to install, just a URL per channel that you can revoke individually.
What it is
A Node.js MCP server that posts to Slack through incoming webhooks. It builds its tool list from your config: every channel you list becomes its own tool, so the model picks the destination by choosing the tool rather than by passing a channel name it might get wrong.
What you get
- One tool per configured channel, named after the key you used — configure channels called general, notifications and alerts and you get
slack_notify_general,slack_notify_notificationsandslack_notify_alerts - A required
messagecarrying the body of the notification - An optional
title, rendered in bold above the message - An optional
colorfor the message sidebar, choosing between good for green, warning for yellow and danger for red — so a failure looks different from a completion at a glance
Requirements
A Slack workspace where you can create incoming webhooks, and one webhook URL per channel you want to reach — created under Apps → Manage → Custom Integrations → Incoming Webhooks. Those URLs go in a config.json in the project directory, copied from the bundled example, each with a display name. Node.js and npm. There is no package to install: clone, npm install, and register index.js with node in your client config.
Setup effort
Build from source — git clone https://github.com/Zavdielx89/slack-notification-mcp.git
USE CASES
01
Being told when a long job finishes
Have the assistant post to your notifications channel at the end of an analysis or build, so you can leave the session and come back to a message.
02
Making failures look like failures
Send errors to the alerts channel with a title and the danger colour, so a red sidebar separates them from routine updates in the same feed.
03
Keeping a team channel updated without switching apps
Post status summaries into the shared channel as work completes, with the headline in the title and the detail in the body.
3 tools
Listed in project docs. Your client may show a different list.
slack_notify_notificationsslack_notify_alertsBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation.
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
# 1. Clone and install
git clone https://github.com/Zavdielx89/slack-notification-mcp.git
cd slack-notification-mcp
npm install
# 2. Configure your Slack webhooks
cp config.example.json config.json
# Edit config.json with your webhook URLs
# 3. Add to your Claude Desktop config
# See detailed setup instructions belowMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"slack-notifications": {
"command": "node",
"args": [
"<YOUR_CLONE_DIRECTORY>/slack-notification-mcp/index.js"
]
}
}
}
