Slack MCP
MCP server that gives AI agents access to your Slack workspaces using session tokens.
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
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。