LabscoMCP early access ↗
atlasfuturesMCP SERVER

Claude MCP Slack

Let an automated Claude Code run download images from Slack with a bot token, into a directory you nominate.

by atlasfutures ↗Team Chat PlatformsCommunity

LABSCO SUMMARY

The missing piece when a GitHub issue points at a Slack screenshot.

It exists for one job: getting a file out of Slack, authenticated, into a place an automated Claude Code run can read it. The token stays a workflow secret and the download directory is validated, so a crafted path cannot write outside where you pointed it.

What it is

A Slack MCP server packaged as a GitHub Action: the action starts it and hands your workflow the MCP config to pass to claude-code-action.

What you get

  • Authenticated downloads of Slack files using a Bot User OAuth token (slack_image_download)
  • A health check on the Slack connection (slack_health_check)
  • A download directory you choose, defaulting to the working directory, with path-traversal validation on it
  • An mcp_config output that drops straight into claude-code-action, alongside other servers
  • A server_executable output and a Docker path, for running it locally or in a container

Requirements

A Slack Bot User OAuth token, the xoxb- kind, supplied as the slack_token input and held as a workflow secret. Used from a workflow that also runs claude-code-action.

Setup effort

Follow the published steps — Create a Slack app at https://api.slack.com/apps → "Create New App" → "From scratch"