About Slack MCP
Slack MCP is an MCP server published by aaronsb in the AI category: model Context Protocol (MCP) server for Slack that implements an OODA Loop pattern for intelligent workspace interaction, supporting both stdio and SSE transports without requiring admin permissions. It has been installed 0 times through Conduid.
The repository has 1 stars and 0 forks, with the last commit a year ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues (0) before depending on it in production.
Install
npx slack-mcpThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
Ask AI about Slack MCP
Powered by Claude · Grounded in docs
Security checks
- ·README presentNot checked yet.
- ·License declaredNot checked yet.
- ·Tests presentNot checked yet.
- ·Dependencies pinnedNot checked yet.
- ·No dynamic code executionNot checked yet.
- !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.
Releases
README
Slack MCP
MCP server that gives AI agents access to your Slack workspaces using session tokens. No OAuth apps, no bot permissions, no admin approval required.
How it works
Slack MCP uses your existing browser session tokens (xoxc/xoxd) to interact with Slack on your behalf. It reads stealthily by default — only the mark-read tool triggers read receipts. Everything else is invisible to other users.
Token extraction is built into the binary. If you're logged into Slack in Chrome or Firefox, the setup flow can extract tokens automatically — no copy-pasting from DevTools.
Prerequisites
You need an active Slack session in your browser. Log into your workspace at app.slack.com in Chrome, Chromium, Edge, or Firefox before running setup.
Install
Claude Code
claude mcp add slack-mcp -- npx -y @aaronsb/slack-mcp
Then ask Claude to run the auth-setup tool. It will guide you through browser selection, profile selection, and automatic token extraction.
Claude Desktop
Download the .mcpb file for your platform from the latest release:
| Platform | File |
|---|---|
| macOS (Apple Silicon) | slack-mcp-darwin-arm64.mcpb |
| macOS (Intel) | slack-mcp-darwin-x64.mcpb |
| Linux (x64) | slack-mcp-linux-x64.mcpb |
| Linux (ARM) | slack-mcp-linux-arm64.mcpb |
| Windows (x64) | slack-mcp-windows-x64.mcpb |
Open the file (double-click or drag into Claude Desktop). When prompted for tokens, you can either:
- Leave them blank and use the
auth-setuptool after connecting - Paste tokens if you already have them
Standalone binary
Download the binary for your platform from releases, then:
# Extract tokens from your browser (interactive)
./slack-mcp setup
# Run as MCP server (stdio, default)
./slack-mcp
# Run as MCP server (SSE, for remote/shared access)
./slack-mcp --transport sse
npm (global)
npm install -g @aaronsb/slack-mcp
slack-mcp setup
Token setup
There are three ways to get your Slack tokens, from easiest to most manual:
Automatic (Chrome/Edge)
The auth-setup MCP tool or slack-mcp setup CLI command will:
- Detect your installed browsers
- Let you pick which browser and profile has Slack
- Open the browser, navigate to Slack, and extract tokens via Chrome DevTools Protocol
- Validate and save them
Requires Chrome to be fully closed before extraction — your tabs will restore when you reopen it.
Semi-automatic (Firefox)
The setup flow writes a temporary browser extension to a temp directory, then guides you to load it in Firefox via about:debugging. The extension extracts tokens and sends them to the local callback server. It's removed automatically when Firefox closes.
Manual
Run slack-mcp setup or use the auth-setup tool — if no browser is detected or automatic extraction fails, it falls back to a localhost web page with step-by-step DevTools instructions.
You can also set tokens directly via environment variables:
export SLACK_MCP_XOXC_TOKEN="xoxc-..."
export SLACK_MCP_XOXD_TOKEN="xoxd-..."
./slack-mcp
Tools
| Tool | What it does |
|---|---|
check-unreads |
Unread messages across DMs, channels, and mentions |
catch-up |
Recent channel activity with time filtering |
list-channels |
Browse channels and membership |
check-mentions |
Your @-mentions grouped by urgency |
search |
Find messages (full Slack query syntax) |
get-context |
Thread history and conversation context |
check-timing |
Conversation pacing analysis |
send-message |
Post to channel, DM, or thread |
mark-read |
Mark conversations as read (only tool that triggers read receipts) |
react |
Add or remove emoji reactions |
auth-setup |
Browser-automated token extraction |
Privacy
- Stealth by default — reads never trigger read receipts; only
mark-readdoes - Channel names, not IDs — the AI never sees internal Slack identifiers
- Tokens stay local — stored in
~/.config/slack-mcp/config.jsonwith0600permissions - No network traffic except Slack — the binary connects only to
slack.com/api/* - No browser downloads — uses your installed browser, never fetches binaries from CDNs
Development
make build # Build for current platform
make test # Run tests
make build-all-platforms # Cross-compile (6 platforms)
make release TAG=v1.3.0 # Tag and push (CI handles the rest)
License
MIT
README mirrored from the source repository 8 hours ago. The original is authoritative.