Server facts
Slack MCP Server
Project
- Author
- korotovsky
- Repository
- github.com/korotovsky/slack-mcp-server
- License
- MIT
- Category
- Communication
Tech
- Runtime / language
- goGo
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 1,867
- Last commit
- Data as of
Tags
- Message Search
- Slack
- Threads
- Workspace Automation
Overview
Slack MCP Server exposes workspace conversations and related directory information to AI assistants. It retrieves channel history and thread replies, including direct and group messages, with pagination based on time windows or message counts. Searches can narrow results by channel, participant, sender, date, or thread membership. Channel names and user lookups are supported alongside identifiers, and cached user details can accompany messages for context. The README also describes unread-message retrieval with priority ordering, mention filtering, and mark-as-read support.
Authentication can use OAuth tokens or browser-session tokens, with different behavior depending on the token type. For example, message search is unavailable with bot tokens, and user search uses either a local cache or Slack's edge API. Write actions are not uniformly enabled: posting messages and adding reactions are disabled by default and can be enabled with channel restrictions. The tool catalog also includes creating and updating user groups, with the relevant OAuth scopes stated. Stdio, SSE, and HTTP transports are supported, as are outgoing proxy settings. However, the supplied README excerpt concentrates on capabilities and tool parameters rather than installation. It contains no runnable server launch command, so an exact startup recipe cannot be supplied from this input. That setup gap is separate from the documented breadth of its workspace toolset.
Install & configure
Requirements
- Access to a Slack workspace
- OAuth or browser-session credentials as described in the README
- An MCP-compatible client
No install command stated in the README — see repo.
A runnable launch command and complete installation procedure are not stated in the provided README excerpt. Stdio, SSE, and HTTP are documented. Posting and reactions require explicit opt-in.
Examples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.
Config file · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Use Settings → Developer → Edit Config when available. Do not assume a Linux configuration path; check the client documentation for your platform. Remote servers use the app’s connector flow when supported, not the local stdio file shown here. Merge this example with existing settings; do not overwrite unrelated servers.
No install command stated in the README — see repo. Check the client documentation for a supported connection method.
Read the Claude Desktop setup guideConfig file · Project: .cursor/mcp.json
User: ~/.cursor/mcp.json
The project path is relative to the workspace root. The tilde denotes your user home directory. Use Cursor’s MCP settings to confirm which configuration and scope your installed version is reading. Merge this example with existing settings; do not overwrite unrelated servers.
No install command stated in the README — see repo. Check the client documentation for a supported connection method.
Read the Cursor setup guideConfig file · Workspace: .vscode/mcp.json
For user scope, use the “MCP: Open User Configuration” command if available. Do not guess a user configuration path across operating systems, profiles, containers, or remote workspaces; check the client documentation. Merge this example with existing settings; do not overwrite unrelated servers.
No install command stated in the README — see repo. Check the client documentation for a supported connection method.
Read the VS Code setup guideConfig file · macOS/Linux: ~/.codeium/windsurf/mcp_config.json
Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json
Open the MCP configuration through Windsurf’s settings when possible to confirm the active file. Paths can differ in managed or future releases; check the client documentation if this location is not present. Merge this example with existing settings; do not overwrite unrelated servers.
No install command stated in the README — see repo. Check the client documentation for a supported connection method.
Read the Windsurf setup guideConfig file · Project scope: .mcp.json at the repository root
The project file uses mcpServers. For user scope, use claude mcp add --scope user rather than assuming .mcp.json in your home directory is the user configuration. Check the client documentation for managed settings and storage details. Merge this example with existing settings; do not overwrite unrelated servers.
No install command stated in the README — see repo. Check the client documentation for a supported connection method.
Read the Claude Code setup guideExamples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.
Tools
Source: repository README. Tool descriptions are a documented snapshot, not a live capability check.
| Tool | What it does |
|---|---|
| conversations_history | Retrieve channel or DM history with time-based or count-based pagination. |
| conversations_replies | Read a conversation thread using its channel and thread timestamp. |
| conversations_add_message | Post text or Markdown after enabling the tool, optionally for selected channels only. |
| conversations_search_messages | Find messages using channel, user, date, and thread filters; unavailable with bot tokens. |
| channels_list | Enumerate selected channel types with optional popularity sorting. |
| reactions_add | Add an emoji reaction when the reaction tool is explicitly enabled. |
| reactions_remove | Remove an emoji reaction under the same opt-in permissions as adding reactions. |
| users_search | Find users by names or email using a token-dependent lookup method. |
| usergroups_list | List workspace user groups, optionally including members or disabled groups. |
| usergroups_create | Create a user group with optional handle, description, and default channels. |
| usergroups_update | Change an existing user group's metadata or default channels. |
| usergroups_users_update | Replace the membership list of a user group. |
Names, permissions, and defaults can change. Check the current upstream documentation before granting access.
Use cases
- Review a channel or DM over a selected time window.
- Find messages by sender, channel, date, or thread.
- Read complete thread context before preparing a response.
- Manage Slack user groups when the required OAuth scopes are granted.
Strengths
- Supports channels, threads, DMs, and group DMs.
- Provides flexible history pagination and detailed search filters.
- Posting and reactions are opt-in and can be restricted to selected channels.
Limitations
- Message search is unavailable with bot tokens.
- User lookup behavior differs between OAuth and browser-session credentials.
- A runnable installation command is not stated in the provided README.
Frequently asked questions
Independent listing, not an affiliation or security review. Grant the least access needed and verify the upstream instructions before running code.
