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.

Slack

Name: Top MCPs — curated MCP directory
Creator: Top MCPs
License: https://creativecommons.org/licenses/by/4.0/

Read and send Slack messages, manage channels and threads.

Score 77(?)Community (korotovsky)MIT 1.6kVerified May 31, 2026Top MCPs for Communication →

Install View on GitHub

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

Not for

Non-Slack messaging platforms
High-security workspaces with API restrictions

Setup recipe

Pick your client, then follow the three steps.

Install

claude_desktop_config.jsonjson

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

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

CLI or .mcp.jsonshell

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

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

.cursor/mcp.jsonjson

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

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

.vscode/mcp.jsonjsonc

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

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

~/.codeium/windsurf/mcp_config.jsonjson

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

Open via Cascade → hammer icon → Configure.

cline_mcp_settings.jsonjson

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

Open via the Cline sidebar → MCP Servers → Edit.

~/.continue/config.jsonjson

{
  "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}"
          }
        }
      }
    ]
  }
}

Continue uses modelContextProtocolServers with a transport block.

~/.codex/config.tomlshell

# ~/.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}" }

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

~/.config/zed/settings.jsonjsonc

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

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

ChatGPT → Apps directorynone

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.

Open in ChatGPT directory

2
Set required secrets
Set SLACK_BOT_TOKEN, SLACK_TEAM_ID in your shell environment before launching your MCP client.
3
Try a minimum working prompt
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.

Tools & permissions

Tools list pending verification. The server exposes tools over MCP; we haven’t yet parsed its capability manifest into this page. Check the GitHub repo for the authoritative list.

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.

Agent prompt pack

— copy into Claude, Cursor, or ChatGPT.

Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.

Recommend the best MCP servers for [task: e.g. communication work] in [client: Claude].

Constraints:
- Prefer tools that are [official | open-source | read-only] — pick what matters for my use case.
- Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport].
- Return at most 3 picks, ranked.

For each pick include:
1. One-sentence rationale.
2. The ready-to-paste install snippet for my client.
3. Any required secrets I need to create before installing.

Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-communication

Compare Slack against a real alternative. Swap the second MCP in [brackets] if you want a different match.

Compare Slack MCP vs [Discord MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"].

Judge them on:
- Setup time and complexity (what a new user hits first).
- Auth model (none / API key / OAuth 2.1) and credential risk.
- Transport (stdio / Streamable HTTP / SSE) and where the server runs.
- Required secrets and the blast radius if they leak.
- Operational risk in an unattended agent loop.
- Which one is "good enough" for a weekend prototype vs. production.

End with one sentence: which should I pick for my scenario, which is: [my scenario].

References:
- https://top-mcps.com/mcp/slack
- top-mcps.com listing for Discord

Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.

Install the Slack MCP server for my [client: Claude] at the default config path for that client.

Use the exact install snippet published at https://top-mcps.com/mcp/slack (fetch https://top-mcps.com/mcp/slack.json for the canonical server.json if you can read URLs).

Before finishing:
1. Create the required secrets (SLACK_BOT_TOKEN, SLACK_TEAM_ID) and put them in the appropriate env block — do not hard-code them.
2. Restart or reload the client so it picks up the new server.
3. Verify the server is connected (green / running state) and at least one tool is listed.
4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry.

Confirm when done and list the tools the server now exposes.

Frequently asked questions

What changed

— 2 updates tracked.

May 31, 2026
Refreshed install snippets and fact sheet; verified for 2026.
Nov 25, 2024
Initial directory listing.

More Communication MCPs

Other tools in the same category worth evaluating.

Discord

Read and post to Discord channels — community management for AI agents.

discordchatcommunitybot

10 minMedium

Send messages and read channel history from a Telegram bot in an agent.

communicationmessagingtelegrambot

6 minLow

Microsoft Teams

Official

Read channel messages, post replies, and trigger meetings from MS Teams.

communicationmicrosoftteamsm365

20 minMedium

Compared with Slack

Side-by-side breakdowns for the choices people most often weigh against this MCP.

SlackvsDiscord SlackvsTeams SlackvsGitHub SlackvsZapier

Exploring Top MCPs for Communication? See all Communication MCPs →