Slack MCP Server
Community MCP server for Slack workspaces - read, search and send messages, no Slack admin approval required.
- Skill Road
- Slack MCP Server
Categories
Description
The Slack MCP server by Dmitrii Korotovskii is a Go-based community project that makes Slack workspaces accessible to AI agents via MCP. It is not an official Slack product - the only previously official reference server is now archived and no longer maintained.
Feature scope
The server supports 18 tools, including retrieving and sending messages, thread replies, reactions, user group management, channel and thread references via #Name and @Lookup, smart history retrieval, and full-text message search.
Three ways to authenticate
A key difference from the classic OAuth app approach: the server accepts bot tokens (xoxb), user OAuth tokens (xoxp), or browser session tokens (xoxc plus xoxd). With the browser-token method, no Slack app creation and no approval by workspace admins is required - though the project itself notes that user or bot tokens are more secure, since they do not depend on an active browser session.
Stdio, SSE, and HTTP transports are supported.
Why a community project instead of an official server
Slack itself does not offer an actively maintained official MCP server; the earlier reference server from the Model Context Protocol project has been archived. For teams that still want to connect Slack to an AI agent, Korotovskii's server is currently the most popular alternative. Important context: without official Slack involvement, there is no guarantee of long-term maintenance or compatibility with future Slack API changes, even though the project is actively developed.
Typical use cases
In practice, the server is useful for having an AI agent automatically respond to questions in specific channels, summarize long threads, forward support requests from a channel into a ticketing system, or post recurring status updates automatically. Because user and browser tokens grant access to private channels and direct messages, the intended scope should be clearly defined in advance.
Frequently asked questions
Is this an official Slack product? No, explicitly not; Slack itself is not involved in this project. Which token type is safest? Per the project documentation, bot or user tokens are preferable since they don't depend on an active browser session. Can the server be used without creating your own Slack app? Yes, via the browser-token method, though at the cost of lower security.
Tools and Safeguards
The server ships with 18 tools, including conversations_history, conversations_replies, conversations_search_messages, channels_list, users_search and several functions for user groups and saved items. Tools that write, such as conversations_add_message, reactions_add and conversations_mark, are disabled by default. You enable them through environment variables such as SLACK_MCP_ADD_MESSAGE_TOOL, and for posting optionally only for selected channels. For sign-in it uses OAuth tokens (xoxp or xoxb) or, in stealth mode, browser tokens (xoxc and xoxd). Stdio, SSE and HTTP are supported, plus proxy and TLS options for corporate networks.
Setup at a glance
For getting started, a single token is usually enough: anyone who only wants to use the server to read and reply to messages in their own bot channel can get by with a bot token and a minimal Slack app without complicated permission management. Anyone who needs full-text search across the whole workspace or access to private channels has to use a user OAuth token instead, accepting the larger security risk of a compromised token. The browser-token method remains more of a stopgap for quick tests when there's no permission to create a Slack app.
Requirements
Node.js 18 or newer to run via npx, or Docker as an alternative. Also requires at least one valid Slack token (xoxb, xoxp, or xoxc plus xoxd).
Installation instructions
This guide covers the community MCP server slack-mcp-server (github.com/korotovsky/slack-mcp-server) by Dmitrii Korotovskii. This is not an official Slack product - the previously official reference server is archived and no longer maintained.
Step 1: Slack MCP: choose a token
The server supports three authentication methods. Pick one:
Bot token (xoxb) - recommended for automation:
Create a Slack app at https://api.slack.com/apps, grant the needed Bot Token Scopes, and install the app in your workspace. The bot must then be manually invited to every channel it should read, and cannot use Slack search.
User OAuth token (xoxp) - full feature set:
Also via a Slack app, but with User Token Scopes instead of Bot Token Scopes. The server then acts with the full permissions of that user, including search.
Browser token (xoxc + xoxd) - no app creation needed:
No Slack app required, but two values must be extracted from your own browser session:
xoxc: In the browser developer tools console, while on Slack, run: JSON.parse(localStorage.localConfig_v2).teams[document.location.pathname.match(/^\/client\/([A-Z0-9]+)/)[1]].token
xoxd: Under the "Application" tab, in Cookies, find the cookie named d and copy its value
The project itself recommends bot or user tokens as the safer choice, since they don't depend on an active browser session.
Step 2: Configuring Slack MCP
{
"mcpServers": {
"slack": {
"command": "npx",
"args": [
"-y",
"slack-mcp-server@latest",
"--transport",
"stdio"
],
"env": {
"SLACK_MCP_XOXP_TOKEN": "xoxp-YOUR-TOKEN"
}
}
}
}
For a bot token, set SLACK_MCP_XOXB_TOKEN instead; for a browser token, set both SLACK_MCP_XOXC_TOKEN and SLACK_MCP_XOXD_TOKEN.
Step 3: Restart your client
Restart your MCP client. The server is then ready to use.
Step 4: Running Slack MCP with Docker
docker pull ghcr.io/korotovsky/slack-mcp-server:latest
Configuration uses the same environment variables, see the official documentation (github.com/korotovsky/slack-mcp-server/blob/master/docs/03-configuration-and-usage.md).
Common questions about token choice, private channels and security are answered in the FAQ section below this guide.
Step 5: Testing after installation
After restarting the client, test with a harmless task to confirm the connection works, such as "List the last five messages in channel #general." If a token error appears, it's usually missing scopes or an expired browser token with the xoxc/xoxd method.
Common pitfalls
With the browser-token method, the xoxd cookie expires after a while once the Slack browser session ends, requiring both values to be re-extracted. With bot tokens, a common mistake is forgetting to invite the bot to the target channel, causing requests to that channel to return empty even though the token itself works fine.
Source: github.com/korotovsky/slack-mcp-server, as of v1.3.0, researched on 2026-09-03.
npx -y slack-mcp-server@latest --transport stdio
Authentication
The server accepts four token types via environment variables, at least one is required: SLACK_MCP_XOXB_TOKEN (bot token, must be invited to channels, cannot search messages), SLACK_MCP_XOXP_TOKEN (user OAuth token, full user permissions including search), or SLACK_MCP_XOXC_TOKEN together with SLACK_MCP_XOXD_TOKEN (browser session token, read from developer tools or cookies of your own Slack session). Per the project documentation, user or bot tokens are preferable, as they do not depend on an active browser session.
Required access permissions
The feature scope depends on the chosen token type. Bot tokens are limited to channels the bot has been invited to and cannot use Slack search. User OAuth and browser tokens act on behalf of the respective Slack user and carry that user’s full access scope, including private channels and direct messages visible to that user.
Transmitted or stored data
The server retrieves messages, channel and user data, and search results via the Slack Web API and forwards them to the MCP client. When using browser tokens, authentication relies on the user’s active Slack browser session rather than a separate app registration.
Security risks
As a community project unaffiliated with Slack, Slack’s own security documentation does not cover this server. With user OAuth and especially browser tokens, the server acts with that person’s full access scope - a compromised token allows reading and writing in every channel and direct message visible to that person. Browser tokens are extracted manually from developer tools and cookies of your own session; the project itself recommends bot or user tokens as the safer alternative. Tokens should be kept only in environment variables and never committed to version control.
License and costs
- License
- MIT
- Cost
- free
The server is open-source and free to use. Costs may arise only from your own runtime environment.
Alternatives
Not recorded yet.
At a glance
- Provider
- Dmitrii Korotovskii
- Status
- Community
- Deployment
- Local and remote
- Current version
- 1.3.0
- GitHub stars
- 1,900
- Last reviewed
- 07.09.2026
Repository and documentation
Categories
Supported clients
Related guides
Guides and background related to this entry.
No related guides yet.