Slack Webhook MCP Server

Connect Slack Webhook MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. A Model Context Protocol (MCP) server that enables LLM applications like Claude Desktop to send messages to Slack channels via incoming webhooks. The slack webhook mcp mcp server is what makes that connection.

What the server does

• Send plain text or markdown-formatted messages to Slack
• Simple and secure webhook URL management
• Built with Deno for modern TypeScript development
• Full test coverage

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Prerequisites — The Prerequisites tool exposed by this server
• Setup — 1. Clone this repository: bash git clone https://github.com/yourusername/slack-webhook-mcp.git cd slack-webhook-mcp
• send_slack_message — The send_slack_message tool exposed by this server

Credentials and setup notes

Configuration is passed through the environment: SLACK_WEBHOOK_URL. 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.

• Deno installed on your system - A Slack workspace with incoming webhooks enabled - Claude Desktop (or another MCP-compatible client)

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Where it fits

Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Slack Webhook MCP's toolset — Prerequisites, Setup, send_slack_message — is a fair guide to whether it matches your workflow. It is maintained by masseater; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.