Slack MCP Server

What the code does

We read the source, 4 d ago · rules 995398eba69f

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

const child = childProcess.spawn(resolveBinaryPath(), process.argv.slice(2), {

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

    cookiesPath := filepath.Join(userDataDir, profileDir, "Cookies")

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add slack-mcp -- npx -y @aaronsb/slack-mcp

{
  "mcpServers": {
    "slack-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@aaronsb/slack-mcp"
      ]
    }
  }
}

[mcp_servers.slack-mcp]
command = "npx"
args = ["-y", "@aaronsb/slack-mcp"]

{
  "mcpServers": {
    "slack-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@aaronsb/slack-mcp"
      ]
    }
  }
}

{
  "servers": {
    "slack-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@aaronsb/slack-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: SLACK_MCP_XOXC_TOKEN (Slack session token. Optional — the auth tool extracts it from your browser and stores it in the config file), SLACK_MCP_XOXD_TOKEN (Slack session cookie. Optional — the auth tool extracts it from your browser and stores it in the config file).