Best for
- Internal collaboration workflows that need channel history or team notifications
- Development teams testing message automation in a non-production workspace
S
58FMRS · C
Channel reads and message actions are useful, but workspace data and write scopes create meaningful risk; OAuth setup and community maintenance also add operational cost.
This community-maintained server connects to a Slack workspace and can list channels, read message history, send messages, and add emoji reactions. It brings assistants into team communication workflows.
Tools
list_channels
List channels in the workspace
post_message
Send a message to a selected channel
get_channel_history
Read a channel's message history
add_reaction
Add an emoji reaction to a message
Setup
Create a Slack App, obtain its Bot Token and Team ID, and pass both values through environment variables.
claude_desktop_config.json
{
"mcpServers": {
"slack": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-slack"],
"env": {
"SLACK_BOT_TOKEN": "xoxb-xxxx",
"SLACK_TEAM_ID": "T0123456"
}
}
}
}
Fit and risk
Not for
- Organizations that prohibit model access to internal chat history
- Workspaces that cannot tightly restrict bot channels and OAuth scopes
Required permissions
- A Slack Bot Token and Team ID
- Least-privilege OAuth scopes for channel history, messages, or reactions
Risks and side effects
- Channel history may contain internal or personally sensitive information
- Messages and reactions are visible to real members; confirm channel and content before writes
Troubleshooting
- Confirm the bot is installed in the target workspace
- Invite the bot to every private channel it needs
- When Slack returns missing_scope, add only the required scope and reinstall the app
Use cases
Summarize the main points from a channel discussion
Post status updates from an on-call workflow
Send meeting notes to a channel
Supported clients
Claude DesktopFull support
CursorPartial support
ClinePartial support