Last reviewed June 2026
Slack is where team communication happens, and connecting Claude to Slack enables message search, summarization, and automated responses. MCP servers provide secure access to your workspace. Here are the best options for Slack integration.
Recommended MCP Servers
Slack MCP (Anthropic)
anthropics/mcp-server-slack
Official Slack integration for reading channels, searching messages, and posting updates.
Key Features
- Read channel messages
- Search across workspace
- Post messages and replies
- Official Anthropic support
Installation
npx @modelcontextprotocol/server-slackThe official Slack MCP from Anthropic provides comprehensive workspace access. Read messages, search history, and post updates. The reliable choice for teams wanting Claude to participate in Slack workflows.
MCP Slack Server
modelcontextprotocol/server-slack
Community Slack server with channel listing, message reading, and search capabilities.
Key Features
- List channels and users
- Read message history
- Search messages
- Thread support
Installation
Configure with Slack Bot TokenA straightforward Slack integration for reading messages and searching history. If you only need Claude to consume Slack content without posting, this provides focused functionality with simpler permissions.
Slack MCP Server
korotovsky/slack-mcp-server
The most powerful MCP server for Slack Workspaces with 1.1k+ stars and stealth mode support.
Key Features
- Channel message access
- Stealth mode (browser tokens)
- Enterprise workspace support
- DMs and Group DMs
Installation
See GitHub for setupThe most powerful Slack MCP with 1.1k+ stars. Features stealth mode using browser tokens, Enterprise workspace support, DMs, Group DMs, and Smart History fetching with pagination.
Quick Comparison
| MCP | Stars | Best For | Pros | Cons |
|---|---|---|---|---|
| Slack MCP (Official) | >2k | Full integration | Read and write | More permissions needed |
| MCP Slack Server | >500 | Read-only access | Simple setup | Limited features |
| Slack MCP (Community) | >200 | Custom needs | Extensible | Community maintained |
Getting Started
To read Slack messages with Claude Code:
Create a Slack App in your workspace with appropriate permissions.
Get your Bot Token from Slack app settings.
Install the Slack MCP:
npx @modelcontextprotocol/server-slackConfigure with your token and start accessing messages.
Example prompt: "Search my Slack workspace for messages about the product launch and summarize the key decisions."
Related Guides
Frequently Asked Questions
What is the best MCP server to read Slack messages with Claude Code?
The korotovsky/slack-mcp-server is the most capable community option, reading channels, threads, DMs, and group DMs with stealth and OAuth modes. For an official route, Slack now hosts its own MCP server at https://mcp.slack.com/mcp. The older @modelcontextprotocol/server-slack reference server is archived and unmaintained, so avoid relying on it.
Can Claude read both Slack channels and direct messages?
Yes. Claude can read public and private channels you have access to, plus direct messages and group DMs, when connected through a Slack MCP server. The korotovsky/slack-mcp-server explicitly supports channels, threads, DMs, and group DMs. Access is always scoped to what the connected user or bot token already has permission to see.
How do I set up a Slack token or app to connect Claude?
Create a Slack app in your workspace, add the scopes you need (such as channels:history, groups:history, and search:read), then install it to get a bot token. Provide that token to your MCP server via environment variables. The korotovsky server also supports a stealth mode using browser session tokens, requiring no app install or admin-granted scopes.
Can Claude post messages to Slack, or only read them?
Claude can do both, but posting is gated for safety. In korotovsky/slack-mcp-server, message posting is disabled by default and must be explicitly enabled. The official Claude Slack connector for Team and Enterprise plans also supports posting and replying in threads. For read-only use, leave write tools disabled and grant only history and search scopes.
