Slack
Team communication layer for reading channels, searching messages, posting updates, and managing threads. Honors Slack rate limits and surfaces ephemeral messages correctly.
INSTALL THIS SERVER
{
"mcpServers": {
"slack": {
"command": "npx",
"args": ["@modelcontextprotocol/server-slack"],
"env": { "SLACK_BOT_TOKEN": "xoxb-your-token" }
}
}
}
9 TOOLS AVAILABLE
OUR ASSESSMENT
- Covers the core Slack API surface (channels, messages, threads, search)
- Built-in rate limit handling
- Thread-aware replies for contextual conversations
- Slack Bot Token requires workspace admin approval
- File uploads and reactions are limited
Uses Slack Bot Tokens with granular OAuth scopes. Scope to the minimum required channels. Bot must be invited to channels before it can read them.
Agents that need to read from and post to Slack channels and threads
TECHNICAL DETAILS
ADOPTION METRICS
// Reading thisModerate star count reflects the communication category niche. Active contributor base with consistent PR cadence.
// Reading thisEnterprise-driven downloads. Teams using Slack as their primary communication layer adopt this for agent-driven channel monitoring.
// Reading this#1 in Communication. The only production-grade Slack MCP.
SOURCES & VERIFICATION
We don't take any single directory's word for it. Before scoring, we cross-reference 2 public MCP sources, install the server ourselves against the clients we cover, and record when we last re-verified.
The same server, 2 different lenses. We reconcile these signals into our editorial score, which is why our number sometimes diverges from a directory-aggregate star count.
| Source | Their rating | Their star count | Their downloads | Last synced |
|---|---|---|---|---|
| AutomationSwitch This page | 4editorial | 980 | 8.4K / wk | APR 22, 2026 |
| Official MCP Registry | — unrated | 980 | unavailable | APR 12, 2026 |
| PulseMCP | 3.9 community | 970 | 7.8K / wk | APR 21, 2026 |
// Counts are directory-reported; we don't adjust them. Discrepancies usually come from different snapshot times or star-caching.
DISCUSS YOUR
MCP REQUIREMENTS.
Evaluating a server, scoping an internal deployment, or working out whether MCP is the right fit at all. Start the conversation and we will point you at the right piece of the ecosystem.