Slack MCP Server (korotovsky)

Add to your client

Copy the config for your MCP client and paste it into its config file.

{
  "mcpServers": {
    "slack-mcp-server-korotovsky": {
      "command": "npx",
      "args": [
        "-y",
        "slack-mcp-server@latest",
        "--transport",
        "stdio"
      ],
      "env": {
        "SLACK_MCP_XOXP_TOKEN": "<your-slack-user-oauth-token-xoxp>"
      }
    }
  }
}

Step-by-step guides: Add to Claude Desktop · Add to Cursor · Add to Windsurf

Before you start

• One Slack auth method: browser tokens (xoxc + xoxd) extracted from the Slack web client, a user OAuth token (xoxp), or a bot token (xoxb, limited to invited channels and no search)
• Go toolchain to build the binary, or Docker, or Node.js/npx to run the npm wrapper
• For xoxc/xoxd: access to your own Slack web session; for xoxp: a Slack app with ~16 user token scopes (channels:history/read, groups, im, mpim, users:read, chat:write, search:read, usergroups:read/write, channels:write)
• An MCP-compatible client (e.g. Claude Desktop)

About Slack MCP Server (korotovsky)

Tools & capabilities (12)

When to use it

• Use it when you need full Slack access — including message search — without getting an admin to approve a bot.
• Use it when an agent should summarize channel or thread history over a time range (e.g. last 7 days).
• Use it when you want to read DMs and group DMs, not just public channels.
• Use it when you need a CSV directory of all workspace channels or users for an agent to reference.
• Use it when you want read-only Slack by default and to opt into posting/reactions deliberately.
• Use it when deploying remotely over SSE/HTTP behind an API key or proxy.

Quick setup

1. 1Choose an auth method: extract xoxc (from localStorage) and xoxd (the `d` cookie) from your Slack web client, or create a Slack app and copy a xoxp user token.
2. 2Run the server via the Go binary, Docker, or the npm wrapper, setting the matching token env vars (SLACK_MCP_XOXC_TOKEN/SLACK_MCP_XOXD_TOKEN or SLACK_MCP_XOXP_TOKEN).
3. 3Optionally enable writes with SLACK_MCP_ADD_MESSAGE_TOOL, SLACK_MCP_REACTION_TOOL, or SLACK_MCP_MARK_TOOL.
4. 4Pick a transport (stdio for desktop clients, or SSE/HTTP with SLACK_MCP_API_KEY for remote).
5. 5Add the server to your MCP client config and restart it.
6. 6Verify by listing channels or fetching recent history from a known channel.

Slack MCP Server (korotovsky) FAQ