Slack MCP Server

What the code does

We read the source, 22 h ago · rules 995398eba69f

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

          fs.writeFileSync(outFd, pdfBuffer);

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

    as_user = '' if user in ('root', pwd.getpwuid(os.getuid()).pw_name) else f'runuser -u {user} -- '

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 fullPath = path.join(stagingDir, filename);

    const child = spawn(process.execPath, [script], {

    wrapper = subprocess.Popen(['bash', '-c', script], start_new_session=True,

  if (isUnder(resolvedAbs, sshDir)) return { hit: true, reason: '~/.ssh/** is sensitive' };

  <script src="https://appsforoffice.microsoft.com/lib/1.1/hosted/office.js"></script>

    const entries = fs.readdirSync(workspacePath, { withFileTypes: true });

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 mcp-server-slack -e 'SLACK_CONFIG_PATH=<SLACK_CONFIG_PATH>' -e 'SLACK_TEAM_ID=<SLACK_TEAM_ID>' -- npx -y @mindstone/mcp-server-slack

{
  "mcpServers": {
    "mcp-server-slack": {
      "command": "npx",
      "args": [
        "-y",
        "@mindstone/mcp-server-slack"
      ],
      "env": {
        "SLACK_CONFIG_PATH": "<SLACK_CONFIG_PATH>",
        "SLACK_TEAM_ID": "<SLACK_TEAM_ID>"
      }
    }
  }
}

[mcp_servers.mcp-server-slack]
command = "npx"
args = ["-y", "@mindstone/mcp-server-slack"]
env = { SLACK_CONFIG_PATH = "<SLACK_CONFIG_PATH>", SLACK_TEAM_ID = "<SLACK_TEAM_ID>" }

{
  "mcpServers": {
    "mcp-server-slack": {
      "command": "npx",
      "args": [
        "-y",
        "@mindstone/mcp-server-slack"
      ],
      "env": {
        "SLACK_CONFIG_PATH": "<SLACK_CONFIG_PATH>",
        "SLACK_TEAM_ID": "<SLACK_TEAM_ID>"
      }
    }
  }
}

{
  "servers": {
    "mcp-server-slack": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@mindstone/mcp-server-slack"
      ],
      "env": {
        "SLACK_CONFIG_PATH": "<SLACK_CONFIG_PATH>",
        "SLACK_TEAM_ID": "<SLACK_TEAM_ID>"
      }
    }
  }
}

Put your own values in place of <SLACK_CONFIG_PATH> (Path to the host-managed Slack config directory), <SLACK_TEAM_ID> (Slack workspace team ID (one process per workspace)). The author’s registry entry marks them as required.

Optional settings from the registry entry, left out of the block above: SLACK_CLIENT_ID (Slack OAuth Connected App client ID. Only required to refresh a rotating token; saved non-rotating tokens authorize the Slack API without it), SLACK_CLIENT_SECRET (Slack OAuth Connected App client secret. Only required to refresh a rotating token; saved non-rotating tokens authorize the Slack API without it), SLACK_DISABLE_REFRESH (Set to 1 to disable token refresh on this surface (cloud surface)), SLACK_REQUEST_TIMEOUT_MS (Override the upstream timeout (max 300000ms = 5 min)), SLACK_MAX_RETRIES (WebClient retries on transient failures (0-20). Lower this on cloud to avoid stacking long retry budgets into multi-minute hangs), MCP_WORKSPACE_PATH (Workspace directory upload_slack_file reads are constrained to (defaults to the system temp dir when unset)).