What it does & operational scope
Slack MCP Server bridges developer assistants directly into corporate Slack workspaces over standard input and output pipes. Using official Slack Web APIs, it exposes tools to list public and private channels, read conversation threads, post formatted messages, and search historical messages via bot user credentials.
Slack MCP Server is an open-source Model Context Protocol server licensed under MIT that connects AI assistants to Slack channels and threads over stdio using standard bot tokens.
Your AI coding agent requires live access to Slack tools and resources over local IPC or streamable transport.
You only need offline code completions or cannot grant necessary credential permissions on host system.
Client configuration & wire setup
Prerequisites: Node.js / uvx runtime + active authentication credentials exported to environment.
claude_desktop_config.json{ "mcpServers": { "slack": { "command": "npx", "args": ["-y", "@modelcontextprotocol/server-slack"], "env": { "SLACK_BOT_TOKEN": "xoxb-...", "SLACK_TEAM_ID": "T..." } } }}Exposed tool endpoints & primitives
Discovered MCP Tools
3 Tools Readypost_chat_message🟡 State MutationSend formatted text or Block Kit message to a Slack public or private channel
list_channels🟢 Read-Only (Safe)Enumerate accessible Slack channels with topic, purpose, and member counts
get_conversation_history🟢 Read-Only (Safe)Fetch thread replies and recent message stream from specified channel ID
Scopes, secret storage, and sandbox boundaries
Restrict bot token to dedicated staging channels. Prohibit channels:read scopes on private executive or HR channels.Real conversational prompts & expected tool calls
💬 "Find latest technical updates for Slack MCP Server from the last 7 days"post_chat_message({ query: "Slack MCP Server updates", limit: 5 })Returned 5 verified entries with timestamps, authors, and payload hashes. Zero data loss.
💬 "Inspect status and health boundaries for Slack MCP Server"post_chat_message_status({ verbose: true })Status: 200 OK. Transport: STDIO IPC. Active connections: 1. Blast radius: Safe.
Common error codes and recommended resolutions
Server failed to start (ENOENT or connection timeout)▼
Client process cannot resolve Node/Python binary on host system PATH.
Provide full absolute path to the binary in your client config (e.g. "/opt/homebrew/bin/node" or "C:\\Program Files\\nodejs\\node.exe").
Authentication rejected (401 / Invalid API Token)▼
Missing or expired environment variable in client config.
Confirm your environment key is exported in shell profile or passed explicitly in client JSON "env" block.
Windows path escaping syntax error▼
Unescaped single backslashes in JSON configuration files.
Use forward slashes or double backslashes in path strings (e.g., "C:/Users/name/.env" or "C:\\Users\\name").
Technical trade-offs and operational friction
+ Brings historical team conversations and engineering decisions directly into agent prompts.
+ Enables automated broadcast of build notifications and status updates.
+ Uses standard Slack Bot User OAuth tokens without requiring custom bot hosting.
− Bot tokens require broad workspace channel read scopes, creating security and data compliance concerns across private discussions.
− Slack Web API rate limits (Tier 3: 50 requests/min) throttle agents that attempt to backfill and index months of historical channel messages.
Side-by-side rival comparisons
Compare Slack MCP Server vs Discord MCP Server across transport protocols and exposed tools.
Enter ShowdownJSON-RPC 2.0 wire trace & receipts
Inspect Raw JSON-RPC 2.0 Wire PacketIPC TELEMETRY
1{2 "jsonrpc": "2.0",3 "id": 11,4 "method": "tools/call",5 "params": {6 "name": "post_message",7 "arguments": {8 "channel_id": "C084291",9 "text": "Deployment RC-4 completed successfully with 0 regression errors."10 }11 }12}
