Slack MCP server: setup, auth, production

What is the Slack MCP server?

A Slack MCP server implements the Model Context Protocol and exposes Slack's capabilities as typed tools an agent can discover and call in the middle of a task. Your team’s messaging and notifications.

Docs and comms access give an agent the context that lives outside the repo — the spec, the decision, the channel where it was made — and a way to report back. Scope to the right spaces and prevent noisy or unauthorized posting.

A real Slack workflow

A long agent task finishes and posts a tidy summary to the right channel; an incident kicks off and the agent drops the timeline as it develops — the agent reports into where the team already works instead of a log nobody reads.

What an agent can do with Slack

• Have an agent post a deploy or incident summary to a channel
• Pull recent discussion for context on a decision
• Notify the right people when a long task finishes

Read-only is the right default: let the agent observe and reason first, then grant specific write actions deliberately — each behind audit logging and, for anything high-impact, human approval.

Setting up the Slack MCP server

Create a Slack app with a bot token carrying only the scopes you need (chat:write to specific channels, history read only if required). Invite the bot to the exact channels — don’t grant workspace-wide posting.

Auth: A Slack app with narrowly scoped bot token permissions. Credentials belong in the environment or a secret store — never in the repo or the agent's sandbox. Wiring a server into Claude Code or Cursor is the same for every tool; the step-by-step lives in the MCP connection guide.

The risk to watch with Slack

The failure mode is noise and reach: a bot that can post anywhere becomes spam or, worse, leaks context into a public channel. Scope to named channels and keep read scopes minimal.

More broadly, a production-grade Slack integration needs channel scoping and preventing noisy or unauthorized posting. The MCP security checklist applies to every integration — we build servers with these controls baked in.