Submit Log in

Slack

by Zencoder

2 views

v0.0.1

MIT

Repository Docs npm

Featured Productivity

slackmessagingcollaborationproductivity

Summary

Read and post to Slack from an AI client — channels, threads, reactions, and user lookup.

Features

List channels and read conversation history
Post messages and threaded replies
Add reactions and look up user profiles

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

Open your agent's MCP configuration file.
Merge the snippet below into it, filling in the environment variables with your own values.
Restart the agent — the "Slack" tools will be available.

{
  "mcpServers": {
    "slack": {
      "command": "npx",
      "args": [
        "-y",
        "@zencoderai/slack-mcp-server"
      ],
      "env": {
        "SLACK_BOT_TOKEN": "xoxb-your-token",
        "SLACK_TEAM_ID": "T01234567"
      }
    }
  }
}

Claude Code

Add the server with a single CLI command.

claude mcp add slack -e SLACK_BOT_TOKEN=xoxb-your-token -e SLACK_TEAM_ID=T01234567 -- npx -y @zencoderai/slack-mcp-server

Claude Desktop

Add the server to claude_desktop_config.json (Settings → Developer → Edit Config).

{
  "mcpServers": {
    "slack": {
      "command": "npx",
      "args": [
        "-y",
        "@zencoderai/slack-mcp-server"
      ],
      "env": {
        "SLACK_BOT_TOKEN": "xoxb-your-token",
        "SLACK_TEAM_ID": "T01234567"
      }
    }
  }
}

Cursor

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

Windsurf

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

VS Code

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

Description

The Slack MCP server, now maintained by Zencoder after being retired from the MCP reference collection, connects an assistant to a Slack workspace.

What it can do

List channels the bot has access to
Read history from a channel or a thread, which is what makes summarising a long discussion possible
Post messages and reply in threads
Add reactions
Look up users and their profiles

Realistic uses

Summarising what happened in a channel while you were away; pulling the decision out of a forty-message thread; posting a build or deploy notification from an agent workflow; and answering questions about past discussions without scrolling.

Setup and permissions

Requires a Slack bot token with scopes matched to what you want it to do, plus the workspace team ID. Scope it narrowly — a bot with channels:history across an entire workspace is a broader grant than most people intend, and the assistant will read whatever it can reach.

Runs with npx -y @zencoderai/slack-mcp-server.

Related MCP Servers

MCP: Google Workspace MCP

by Google

New

Google's own remote MCP endpoints for Gmail, Drive, Docs, Sheets, Slides, Calendar, Chat and People — OAuth 2.0, hosted by Google, no server to run.

Productivity

MCP: Zapier MCP

by Zapier

New

Zapier's official hosted MCP server, exposing actions across 8,000+ connected apps as agent tools — with you choosing exactly which actions each server may perform.

Productivity