> mcp integration
Slack MCP Server: What It Does & How to Use It with Claude
What the Slack MCP server can do — search, post, read threads, manage channels — and how to connect it to Claude Cowork, Claude Code, or Claude Desktop.
The Slack MCP server lets an AI assistant work inside your Slack workspace: searching messages, reading channels and threads, posting and drafting messages, managing channels, and creating canvases. Connect it to Claude Cowork, Claude Code, or Claude Desktop and you can ask Claude to find, summarize, and act on Slack in plain language.
What the Slack MCP server can do
As of the May 2026 tools update, the server exposes (across the official and community versions):
| Capability | What it enables |
|---|---|
| Search | Search messages and files by date/user/content; search channels by name/description; list users and custom emoji |
| Read | Read full channel history and thread conversations; read files; read user profiles and channel members |
| Write | Send messages to any conversation; draft messages (preview in the client before sending); add emoji reactions |
| Manage | Create channels, group DMs, and IM conversations; list channel members |
| Canvases | Create and update canvases as rich documents; read canvases exported as Markdown |
In practice that means Claude can answer “what did the #launch channel decide yesterday?”, draft a reply for your review, or roll a thread into a canvas summary, all without you leaving the assistant.
Official vs community server
- Official Slack MCP server (
docs.slack.dev/ai/slack-mcp-server). The right default: maintained by Slack, predictable permissions, canvases and search built in. - Community
korotovsky/slack-mcp-serveradds DMs, group DMs, GovSlack, and a no-extra-permissions setup with smart history fetching. Reach for it when the official scopes don’t cover your use case.
How to connect it to Claude (Cowork / Code / Desktop)
- Choose the server (official for most teams) and install the Slack app / obtain a token with the minimum scopes you need.
- Register the MCP server with your client: in Claude Cowork and Claude Desktop via the MCP settings, or in Claude Code via
claude mcp add. - Start read-only against a single channel, confirm it behaves, then widen scope.
How we use it: three workflows it’s genuinely good for. (1) “summarize what #launch decided since yesterday” before standup; (2) draft-and-preview a reply without leaving the assistant; (3) roll a long thread into a canvas summary. Where it struggles: bulk history search is rate-limited, and the official server is channel-scoped, so DM access needs the community server. Our default is the official server in Claude Cowork for search/summarize, and Claude Code when scripting Slack into an agent workflow. Start read-only, and never grant DM access unless a workflow truly needs it.
Security & permissions
Treat Slack like production data: request the narrowest scopes, default to read-only, keep DM access off unless required, and prefer admin-approved app installs over personal tokens for anything shared.
Wiring Slack into your stack
If you’d rather have Slack (and the rest of your tools) wired into a Claude setup that actually fits your workflows, scoped safely and maintained, that’s what we do. Book a discovery call.
Sources: Slack MCP server overview · Slack’s guide · New MCP tools, May 2026 · korotovsky/slack-mcp-server.