# Slack

> Read and send Slack messages, manage channels and threads.

[Canonical HTML page](https://top-mcps.com/mcp/slack) · [server.json](https://top-mcps.com/mcp/slack.json) · [methodology](https://top-mcps.com/about/methodology)

## Install

### Claude Desktop — `claude_desktop_config.json`

Paste under mcpServers. Fully quit and reopen Claude after editing.

```json
{
  "mcpServers": {
    "slack": {
      "command": "npx",
      "args": [
        "-y",
        "slack-mcp-server"
      ],
      "env": {
        "SLACK_BOT_TOKEN": "${SLACK_BOT_TOKEN}",
        "SLACK_TEAM_ID": "${SLACK_TEAM_ID}"
      }
    }
  }
}
```

### Claude Code — `CLI or .mcp.json`

Run from your repo. Commit .mcp.json to share with your team.

```shell
# export SLACK_BOT_TOKEN=xoxb-your-bot-token
# export SLACK_TEAM_ID=T0000000
claude mcp add slack -- npx -y slack-mcp-server
```

### Cursor — `.cursor/mcp.json`

Global path: ~/.cursor/mcp.json. Reload window after editing.

```json
{
  "mcpServers": {
    "slack": {
      "command": "npx",
      "args": [
        "-y",
        "slack-mcp-server"
      ],
      "env": {
        "SLACK_BOT_TOKEN": "${SLACK_BOT_TOKEN}",
        "SLACK_TEAM_ID": "${SLACK_TEAM_ID}"
      }
    }
  }
}
```

### VS Code — `.vscode/mcp.json`

VS Code uses the "servers" key (not "mcpServers").

```jsonc
{
  "servers": {
    "slack": {
      "command": "npx",
      "args": [
        "-y",
        "slack-mcp-server"
      ],
      "env": {
        "SLACK_BOT_TOKEN": "${SLACK_BOT_TOKEN}",
        "SLACK_TEAM_ID": "${SLACK_TEAM_ID}"
      }
    }
  }
}
```

### Windsurf — `~/.codeium/windsurf/mcp_config.json`

Open via Cascade → hammer icon → Configure.

```json
{
  "mcpServers": {
    "slack": {
      "command": "npx",
      "args": [
        "-y",
        "slack-mcp-server"
      ],
      "env": {
        "SLACK_BOT_TOKEN": "${SLACK_BOT_TOKEN}",
        "SLACK_TEAM_ID": "${SLACK_TEAM_ID}"
      }
    }
  }
}
```

### Cline — `cline_mcp_settings.json`

Open via the Cline sidebar → MCP Servers → Edit.

```json
{
  "mcpServers": {
    "slack": {
      "command": "npx",
      "args": [
        "-y",
        "slack-mcp-server"
      ],
      "env": {
        "SLACK_BOT_TOKEN": "${SLACK_BOT_TOKEN}",
        "SLACK_TEAM_ID": "${SLACK_TEAM_ID}"
      }
    }
  }
}
```

### Continue — `~/.continue/config.json`

Continue uses modelContextProtocolServers with a transport block.

```json
{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "slack-mcp-server"
          ],
          "env": {
            "SLACK_BOT_TOKEN": "${SLACK_BOT_TOKEN}",
            "SLACK_TEAM_ID": "${SLACK_TEAM_ID}"
          }
        }
      }
    ]
  }
}
```

### Codex CLI — `~/.codex/config.toml`

Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

```shell
# ~/.codex/config.toml
[mcp_servers.slack]
command = "npx"
args = [
  "-y",
  "slack-mcp-server",
]
env = { SLACK_BOT_TOKEN = "${SLACK_BOT_TOKEN}", SLACK_TEAM_ID = "${SLACK_TEAM_ID}" }
```

### Zed — `~/.config/zed/settings.json`

Zed calls them "context_servers". Settings live-reload on save.

```jsonc
{
  "context_servers": {
    "slack": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "slack-mcp-server"
        ]
      },
      "env": {
        "SLACK_BOT_TOKEN": "${SLACK_BOT_TOKEN}",
        "SLACK_TEAM_ID": "${SLACK_TEAM_ID}"
      }
    }
  }
}
```

### ChatGPT — `ChatGPT → Apps directory`

Slack is also available in the official ChatGPT Apps directory — no manual setup, no Developer mode required. Open the app from the directory and grant access on first use.

```none

```

## At a glance

- **Maintainer:** Community (korotovsky)
- **Transport:** stdio
- **Auth model:** API key
- **Required secrets:** SLACK_BOT_TOKEN, SLACK_TEAM_ID
- **Supported clients:** Claude, Any MCP-compatible client, Slack workspaces
- **License:** MIT
- **Language:** TypeScript
- **Latest version:** latest
- **Last verified:** 2026-05-31
- **GitHub stars:** 1,639 (fetched 2026-06-02T11:55:51.691Z)
- **Score:** 77/100 (rubric 2026-04 — see https://top-mcps.com/about/methodology)
- **Source:** https://github.com/korotovsky/slack-mcp-server

## Security & scope

- **Access scope:** network
- **Sandbox:** Authenticates to Slack with a bot token (xoxb-...). Acts under the bot identity in whichever workspace installed the app; scope limited by the bot user scopes.
- **Gotchas:**
  - Bot-authored messages appear under the bot, not under your personal Slack identity.
  - DMs require the bot to be invited; uninvited DMs return a 404.
  - Workspace admins can audit every bot token call — treat agent actions as auditable.

## Quick answer

**What it does.** Provides access to Slack channels, messages, threads, users, and workspace data via the Slack Web API.

**Best for:**
- Automated Slack notifications
- Channel monitoring
- Message summarization
- Thread management
- Team communication automation

**Not for:**
- Non-Slack messaging platforms
- High-security workspaces with API restrictions

## Recipes

### Post a concise standup update to a channel

```
Summarise what I worked on today from the last 10 commits on the current repo and post a 3-bullet standup update to #team-eng. Keep it under 500 characters and end with blockers or an "all clear" line.
```

_Tested with: Claude Desktop, Cursor_

## Description

The Slack MCP connects AI models to your Slack workspace via the Slack API. Read channel messages, post to channels, manage threads, and search messages — all from an AI context. Useful for agents that need to monitor or participate in team communication.

## Why it matters

Teams run on Slack. This MCP lets AI agents participate in and extract information from team communication without manual copy-pasting.

## Key features

- Channel read/write access
- Thread management
- Message search
- User lookup
- Slack API integration

## FAQ

### What Slack permissions are needed?

At minimum: `channels:read`, `channels:history`, `chat:write`, `users:read`, and `search:read`. For private channels add `groups:read` and `groups:history`. Issue a Bot Token (`xoxb-…`) on a custom Slack app, not a user token.

### Can it post to private channels?

Yes, but the bot user must first be invited to each private channel — Slack does not grant access to private channels via scopes alone. Run `/invite @your-bot` in each private channel you want the agent to reach.

### Does it need the workspace ID?

Yes, pass it as `SLACK_TEAM_ID` (format `T0…`). You can find it in the Slack admin panel or by running `team.info` via the API. Without it the server cannot scope lookups and will fail on multi-team installs.

### Will it show the agent as a human user?

No. Bot Tokens always post as the app, not as you. For agents, that is the right thing — auditors can tell apart bot-authored messages from human ones by the `app` flag in the Slack UI.

### Can it listen for messages (not just send)?

This MCP polls via REST — `conversations.history`, `search.messages`. It does not hold a Socket Mode or Events API connection. For real-time event handling, run a small Slack app alongside it and let the MCP act on the state your app has captured.

## Changelog

- **2026-05-31** — Refreshed install snippets and fact sheet; verified for 2026.
- **2024-11-25** — Initial directory listing.