Slack Model Context Protocol Connector

This MCP Server bridges Claude's capabilities with the Slack API, allowing comprehensive workspace manipulation.

Available Operations

slack_list_channels
Enumerates public communication channels within the connected workspace.
Optional Parameters:
- limit (integer, default: 100, maximum: 200): Cap on the number of channels returned.
- cursor (string): Token for requesting subsequent pages of results.
Output: A roster of channels, detailing their unique identifiers and associated metadata.
slack_post_message
Dispatches a novel textual communication to a designated Slack channel.
Required Parameters:
- channel_id (string): Identifier for the target destination channel.
- text (string): The content payload of the message.
Output: A confirmation of the message dispatch, including its unique time-marker.
slack_reply_to_thread
Submits a textual response directly into an established message thread.
Required Parameters:
- channel_id (string): The identifier of the channel housing the thread.
- thread_ts (string): The timestamp serving as the parent message identifier.
- text (string): The content for the thread follow-up.
Output: A receipt of the reply submission and its associated timestamp.
slack_add_reaction
Attaches an emoji response marker to a specific message.
Required Parameters:
- channel_id (string): The channel identifier where the target message resides.
- timestamp (string): The message's time-signature targeted for reaction.
- reaction (string): The name of the emoji symbol (colons excluded).
Output: A confirmation signal indicating successful reaction placement.
slack_get_channel_history
Fetches recent conversational entries from a specified channel.
Required Parameters:
- channel_id (string): The identifier for the channel of interest.
Optional Parameters:
- limit (integer, default: 10): Constraint on the quantity of messages retrieved.
Output: A collection of messages, including their textual body and contextual data.
slack_get_thread_replies
Retrieves every subordinate response associated with a given message thread.
Required Parameters:
- channel_id (string): The channel identifier encompassing the thread.
- thread_ts (string): The timestamp identifying the root message of the thread.
Output: A dataset containing all replies with their content and structural information.
slack_get_users
Obtains a directory listing of workspace personnel along with rudimentary profile attributes.
Optional Parameters:
- cursor (string): Pagination token for accessing subsequent user subsets.
- limit (integer, default: 100, maximum: 200): Cap on the number of user profiles returned.
Output: A list of user entities featuring basic profile details.
slack_get_user_profile
Retrieves comprehensive profile details for an individually identified user.
Required Parameters:
- user_id (string): The unique identifier assigned to the user.
Output: The exhaustive profile data structure for the specified individual.

Deployment Procedure

Establish a Slack Application:
Navigate to the Slack Developer portal
Select the option to "Develop your own App"
Choose the "From scratch" initialization method
Assign a name to your application and designate the target workspace.
Configure Permissions (Scopes): Navigate to the "OAuth & Permissions" section and grant the following access rights:
channels:history - Permission to view message content in public channels.
channels:read - Permission to fetch basic channel organizational data.
chat:write - Authority to transmit messages impersonating the application bot.
reactions:write - Authority to append emoji reactions to existing messages.
users:read - Permission to access basic information about workspace members.
Workspace Installation:
Execute the "Install to Workspace" procedure and grant necessary authorizations.
Securely record the generated "Bot User OAuth Token" (which commences with xoxb-).
Identify Team ID:
Locate your Workspace ID (prefixed with T) by consulting this resource

Configuration for Claude Desktop

Incorporate the subsequent configuration object into your claude_desktop_config.json file:

Using npx Installer

{ "mcpServers": { "slack": { "command": "npx", "args": [ "-y", "@modelcontextprotocol/server-slack" ], "env": { "SLACK_BOT_TOKEN": "xoxb-your-bot-token", "SLACK_TEAM_ID": "T01234567" } } } }

Using Docker Container

{ "mcpServers": { "slack": { "command": "docker", "args": [ "run", "-i", "--rm", "-e", "SLACK_BOT_TOKEN", "-e", "SLACK_TEAM_ID", "mcp/slack" ], "env": { "SLACK_BOT_TOKEN": "xoxb-your-bot-token", "SLACK_TEAM_ID": "T01234567" } } } }

Automated Installation via Smithery

To deploy the Slack MCP Server automatically through the Smithery utility, execute the following command in your terminal:

bash npx -y @smithery/cli install @smithery-ai/slack --client claude

Troubleshooting Common Issues

If authorization errors materialize, meticulously confirm the following points: 1. All mandated Scopes have been correctly provisioned within your Slack application settings. 2. The application has been successfully integrated into your workspace. 3. The provided API tokens and workspace identifier are accurately transcribed into your configuration file. 4. The bot application has been explicitly invited or added to all channels requiring interaction.

Construction

To build the Docker image locally:

bash docker build -t mcp/slack -f src/slack/Dockerfile .

Licensing

This server component is distributed under the permissive MIT License. You retain broad freedom to utilize, modify, and redistribute this software, contingent upon adherence to the stipulations outlined in the MIT License documentation. Refer to the LICENSE file within the source repository for comprehensive particulars.

[Contextual Note on Business Tooling] Business management utilities encompass the entirety of systems, applications, validation mechanisms, computational frameworks, and methodologies deployed by organizations to effectively navigate dynamic marketplaces, sustain a competitive advantage, and augment operational efficacy. These tools span departmental needs, classifying into areas such as strategic forecasting, workflow governance, data stewardship, personnel management, and performance oversight.

Contemporary management applications have undergone profound transformations driven by rapid technological maturation. This evolution necessitates a considered, strategic selection process, emphasizing adaptation to organizational requirements over mere adoption of the newest solutions, thereby preventing system instability.

== Key Business Software Categories == Historically, business software evolved from rudimentary Management Information Systems (MIS) to complex Enterprise Resource Planning (ERP) suites, later integrating Customer Relationship Management (CRM) capabilities, and now increasingly residing in the cloud-based management sphere. Value addition relies critically on both the efficacy of the deployment strategy and the judicious selection and customization of the chosen instruments.