Slack
Enables interaction with Slack workspaces, providing tools to list channels, post messages, reply to threads, add emoji reactions, retrieve channel history, get thread replies, list workspace users, and access user profile information.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Slack post a message to the general channel reminding everyone about the 2pm meeting"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
slack-mcp-server
Disclaimer
This project includes code originally developed by Anthropic and released under the MIT License. Substantial modifications and new functionality have been added by For Good AI Inc. (dba Zencoder Inc.), and are licensed under the Apache License, Version 2.0.
Related MCP server: slack-mcp-claude-auth
Overview
A Model Context Protocol (MCP) server for interacting with Slack workspaces. This server provides tools to list channels, post messages, reply to threads, add reactions, get channel history, and manage users.
Available Tools
slack_list_channels
List public or pre-defined channels in the workspace
Optional inputs:
limit(number, default: 100, max: 200): Maximum number of channels to returncursor(string): Pagination cursor for next page
Returns: List of channels with their IDs and information
slack_post_message
Post a new message to a Slack channel
Required inputs:
channel_id(string): The ID of the channel to post totext(string): The message text to post
Returns: Message posting confirmation and timestamp
slack_reply_to_thread
Reply to a specific message thread
Required inputs:
channel_id(string): The channel containing the threadthread_ts(string): Timestamp of the parent messagetext(string): The reply text
Returns: Reply confirmation and timestamp
slack_add_reaction
Add an emoji reaction to a message
Required inputs:
channel_id(string): The channel containing the messagetimestamp(string): Message timestamp to react toreaction(string): Emoji name without colons
Returns: Reaction confirmation
slack_get_channel_history
Get recent messages from a channel
Required inputs:
channel_id(string): The channel ID
Optional inputs:
limit(number, default: 10): Number of messages to retrieve
Returns: List of messages with their content and metadata
slack_get_thread_replies
Get all replies in a message thread
Required inputs:
channel_id(string): The channel containing the threadthread_ts(string): Timestamp of the parent message
Returns: List of replies with their content and metadata
slack_get_users
Get list of workspace users with basic profile information
Optional inputs:
cursor(string): Pagination cursor for next pagelimit(number, default: 100, max: 200): Maximum users to return
Returns: List of users with their basic profiles
slack_get_user_profile
Get detailed profile information for a specific user
Required inputs:
user_id(string): The user's ID
Returns: Detailed user profile information
Slack Bot Setup
To use this MCP server, you need to create a Slack app and configure it with the necessary permissions:
1. Create a Slack App
Visit the Slack Apps page
Click "Create New App"
Choose "From scratch"
Name your app and select your workspace
2. Configure Bot Token Scopes
Navigate to "OAuth & Permissions" and add these scopes:
channels:history- View messages and other content in public channelschannels:read- View basic channel informationchat:write- Send messages as the appreactions:write- Add emoji reactions to messagesusers:read- View users and their basic informationusers.profile:read- View detailed profiles about users
3. Install App to Workspace
Click "Install to Workspace" and authorize the app
Save the "Bot User OAuth Token" that starts with
xoxb-
4. Get Your Team ID
Get your Team ID (starts with a T) by following this guidance
5. Add Bot to Channels (Optional)
For the bot to access private channels or to post messages, you may need to invite it to specific channels using /invite @your-bot-name
Features
Multiple Transport Support: Supports both stdio and Streamable HTTP transports
Modern MCP SDK: Updated to use the latest MCP SDK (v1.13.2) with modern APIs
Comprehensive Slack Integration: Full set of Slack operations including:
List channels (with predefined channel support)
Post messages
Reply to threads
Add reactions
Get channel history
Get thread replies
List users
Get user profiles
Installation
Local Development
npm install
npm run buildGlobal Installation (NPM)
npm install -g @zencoderai/slack-mcp-serverDocker Installation
# Build the Docker image locally
docker build -t slack-mcp-server .
# Or pull from Docker Hub
docker pull zencoderai/slack-mcp:latest
# Or pull a specific version
docker pull zencoderai/slack-mcp:1.0.0Configuration
Set the following environment variables:
export SLACK_BOT_TOKEN="xoxb-your-bot-token"
export SLACK_TEAM_ID="your-team-id"
export SLACK_CHANNEL_IDS="channel1,channel2,channel3" # Optional: predefined channels
export AUTH_TOKEN="your-auth-token" # Optional: Bearer token for HTTP authorization (Streamable HTTP transport only)Usage
Command Line Options
slack-mcp [options]
Options:
--transport <type> Transport type: 'stdio' or 'http' (default: stdio)
--port <number> Port for HTTP server when using Streamable HTTP transport (default: 3000)
--token <token> Bearer token for HTTP authorization (optional, can also use AUTH_TOKEN env var)
--help, -h Show this help messageLocal Usage Examples
Using the slack-mcp command (after global installation)
# Use stdio transport (default)
slack-mcp
# Use stdio transport explicitly
slack-mcp --transport stdio
# Use Streamable HTTP transport on default port 3000
slack-mcp --transport http
# Use Streamable HTTP transport on custom port
slack-mcp --transport http --port 8080
# Use Streamable HTTP transport with custom auth token
slack-mcp --transport http --token mytoken
# Use Streamable HTTP transport with auth token from environment variable
AUTH_TOKEN=mytoken slack-mcp --transport httpUsing node directly (for development)
# Use stdio transport (default)
node dist/index.js
# Use stdio transport explicitly
node dist/index.js --transport stdio
# Use Streamable HTTP transport on default port 3000
node dist/index.js --transport http
# Use Streamable HTTP transport on custom port
node dist/index.js --transport http --port 8080
# Use Streamable HTTP transport with custom auth token
node dist/index.js --transport http --token mytoken
# Use Streamable HTTP transport with auth token from environment variable
AUTH_TOKEN=mytoken node dist/index.js --transport httpDocker Usage Examples
Using Docker directly
# Run with stdio transport (default)
docker run --rm \
-e SLACK_BOT_TOKEN="xoxb-your-bot-token" \
-e SLACK_TEAM_ID="your-team-id" \
zencoderai/slack-mcp:latest
# Run with HTTP transport on port 3000
docker run --rm -p 3000:3000 \
-e SLACK_BOT_TOKEN="xoxb-your-bot-token" \
-e SLACK_TEAM_ID="your-team-id" \
zencoderai/slack-mcp:latest --transport http
# Run with HTTP transport on custom port
docker run --rm -p 8080:8080 \
-e SLACK_BOT_TOKEN="xoxb-your-bot-token" \
-e SLACK_TEAM_ID="your-team-id" \
zencoderai/slack-mcp:latest --transport http --port 8080
# Run with custom auth token
docker run --rm -p 3000:3000 \
-e SLACK_BOT_TOKEN="xoxb-your-bot-token" \
-e SLACK_TEAM_ID="your-team-id" \
-e AUTH_TOKEN="mytoken" \
zencoderai/slack-mcp:latest --transport httpUsing Docker Compose
Create a docker-compose.yml file:
version: '3.8'
services:
slack-mcp:
# Use published image:
image: zencoderai/slack-mcp:latest
# Or build locally:
# build: .
environment:
- SLACK_BOT_TOKEN=xoxb-your-bot-token
- SLACK_TEAM_ID=your-team-id
- SLACK_CHANNEL_IDS=channel1,channel2,channel3 # Optional
- AUTH_TOKEN=your-auth-token # Optional for HTTP transport
ports:
- "3000:3000" # Only needed for HTTP transport
command: ["--transport", "http"] # Optional: specify transport type
restart: unless-stoppedThen run:
# Start the service
docker compose up -d
# View logs
docker compose logs -f slack-mcp
# Stop the service
docker compose downTransport Types
Stdio Transport
Use case: Command-line tools and direct integrations
Communication: Standard input/output streams
Default: Yes
Streamable HTTP Transport
Use case: Remote servers and web-based integrations
Communication: HTTP POST requests with optional Server-Sent Events streams
Features:
Session management
Bidirectional communication
Resumable connections
RESTful API endpoints
Bearer token authentication
Authentication (Streamable HTTP Transport Only)
When using Streamable HTTP transport, the server supports Bearer token authentication:
Command Line: Use
--token <token>to specify a custom tokenEnvironment Variable: Set
AUTH_TOKEN=<token>as a fallbackAuto-generated: If neither is provided, a random token is generated
The command line option takes precedence over the environment variable. Include the token in HTTP requests using the Authorization: Bearer <token> header.
Troubleshooting
If you encounter permission errors, verify that:
All required scopes are added to your Slack app
The app is properly installed to your workspace
The tokens and workspace ID are correctly copied to your configuration
The app has been added to the channels it needs to access
Development
Build
npm run buildWatch Mode
npm run watchAPI Endpoints (Streamable HTTP Transport)
When using Streamable HTTP transport, the server exposes the following endpoints:
POST /mcp- Client-to-server communicationGET /mcp- Server-to-client notifications (Server-Sent Events streams)DELETE /mcp- Session termination
Changes from Previous Version
Updated MCP SDK: Upgraded from v1.0.1 to v1.13.2
Modern API: Migrated from low-level Server class to high-level McpServer class
Zod Validation: Added proper schema validation using Zod
Transport Flexibility: Added support for Streamable HTTP transport
Command Line Interface: Added CLI arguments for transport selection
Session Management: Implemented proper session handling for HTTP transport
Better Error Handling: Improved error handling and logging
Available Tools
8 toolsslack_add_reactionAdd Slack ReactionB
Add a reaction emoji to a message
Inputs: channel_id (required), timestamp (required), reaction (required).
slack_get_channel_historyGet Slack Channel HistoryC
Get recent messages from a channel
Inputs: channel_id (required), limit.
slack_get_thread_repliesGet Slack Thread RepliesA
Get all replies in a message thread
Inputs: channel_id (required), thread_ts (required).
slack_get_user_profileGet Slack User ProfileB
Get detailed profile information for a specific user
Inputs: user_id (required).
slack_get_usersGet Slack UsersA
Get a list of all users in the workspace with their basic profile information
Inputs: cursor, limit.
slack_list_channelsList Slack ChannelsB
List public and private channels that the bot is a member of, or pre-defined channels in the workspace with pagination
Inputs: limit, cursor.
slack_post_messagePost Slack MessageB
Post a new message to a Slack channel or direct message to user
Inputs: channel_id (required), text (required).
slack_reply_to_threadReply to Slack ThreadB
Reply to a specific message thread in Slack
Inputs: channel_id (required), thread_ts (required), text (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: reacting, reading history, threads, user info, channels, posting, and replying. No overlap or ambiguity.
All tools follow a consistent verb_noun pattern with a 'slack_' prefix (e.g., slack_post_message, slack_list_channels). No mixing of styles.
8 tools is well-scoped for a Slack MCP server, covering essential operations without being too many or too few.
Core CRUD for messaging and user info is covered. Minor gaps exist (e.g., editing/deleting messages, creating channels), but the surface is sufficient for typical workflow.
Maintenance
Related MCP Connectors
Hosted Slack MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
Enable interaction with Slack workspaces. Supports subscribing to Slack events through Resources.
Talk to your public-facing AI from any MCP client — Claude, ChatGPT, Cursor, Cline, Windsurf.
IRC-style chat server where AI agents and people talk: channels, DMs, claims, approvals.
Related MCP Servers
- AlicenseBqualityDmaintenanceA Model Context Protocol server implementation that enables AI assistants to interact with Slack workspaces, allowing them to browse channels, send messages, reply to threads, add reactions, and retrieve user information.953 npm2Apache 2.0
- FlicenseNot gradedqualityDmaintenanceLocal stdio MCP proxy for the official Slack MCP endpoint, using Claude's Slack plugin for authentication to enable Slack integration via MCP without needing a custom Slack app.-
- AlicenseAqualityBmaintenanceLocal MCP stdio bridge to Slack's hosted MCP server, enabling agents to use Slack tools (send messages, search, history, canvas, etc.) via local OAuth and token refresh.850 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to interact with Slack workspaces by listing channels, posting messages and thread replies, adding emoji reactions, retrieving channel history and thread replies, and inspecting user profiles. Supports both stdio and Streamable HTTP transports for flexible integration.MIT