Slack MCP Server

What it does

• Channel/message ops: list channels, post, reply to threads, reactions, history, users, profiles
• Maintained Zencoder fork of the archived Anthropic slack server (Apache-2.0 additions)
• stdio by default; `--transport http` for Streamable HTTP with Bearer auth

When to use it

The standard 'Claude reads/writes my Slack' server: digest a channel, post a status update, triage threads. Requires a Slack app + bot token, so it's a real setup task, not a drop-in.

Getting started

Create a Slack app with scopes channels:history, channels:read, chat:write, reactions:write, users:read, users.profile:read; install to workspace; grab the xoxb- token and your team ID. Then:

{
  "command": "npx",
  "args": ["-y", "@zencoderai/slack-mcp-server"],
  "env": { "SLACK_BOT_TOKEN": "xoxb-...", "SLACK_TEAM_ID": "T..." }
}

Things to know

Write tools are real writes — slack_post_message posts as your bot in your workspace. Private channels need a manual /invite. HTTP transport without AUTH_TOKEN is unauthenticated; keep it stdio unless you add auth.