# Slack MCP [Official] [Health: Active]

**Category:** 💬 Communication  
**Repository:** https://docs.slack.dev/ai/slack-mcp-server/  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/slack-mcp

## Description
Slack's official hosted MCP server. Lets MCP clients search channels, read and send messages, and take other Slack actions over OAuth, with workspace admins approving and managing each client integration.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What Slack MCP does

Slack MCP gives MCP-compatible clients access to Slack workspace capabilities through an official hosted MCP server. Its primary functions cover searching channels, reading messages, and sending messages. It also exposes additional Slack actions supported by the service, allowing an agent to work with Slack through MCP rather than through a separate custom integration.

The server is intended for use cases where an AI client needs to find relevant Slack discussions, inspect message content, or post messages. Because access is tied to a Slack workspace and managed through an approval process, it fits teams that want administrators involved in deciding which client integrations can connect.

## How it works

An MCP client connects to Slack MCP and authorizes access using OAuth. The OAuth flow establishes the connection between the client and the Slack workspace. After authorization, the agent can invoke the available Slack tools from its MCP session.

Workspace administrators approve and manage each client integration. This places workspace-level control around agent access instead of treating every client connection as an unmanaged Slack application. The result is a hosted connection pattern: the MCP client uses Slack MCP as the intermediary for supported Slack operations.

## Setup and configuration

Use a compatible MCP client that can connect to the hosted Slack MCP service. Authorize the connection with OAuth, then complete any approval required by the Slack workspace administrator. Administrators are responsible for approving and managing client integrations for their workspace.

No local runtime or environment-variable configuration is described for using the hosted service. The important setup steps are client connection, OAuth authorization, and workspace approval.

## Tools and capabilities

Slack MCP supports agent access to these categories of Slack operations:

- Search channels for relevant Slack content.
- Read messages from Slack.
- Send messages to Slack.
- Use other Slack actions exposed by the hosted service.

These capabilities allow an agent to retrieve workspace context and take message-oriented actions from an MCP client.

## Limitations and notes

Access depends on OAuth authorization and workspace administrator approval. Administrators also control the client integrations connected to their workspace. The available actions are limited to the tools exposed by Slack MCP, so an agent should be evaluated against the specific Slack operation it needs before adoption.

Slack MCP is hosted, which makes it different from a locally configured server that an operator runs and maintains. Its main value is the managed connection between an MCP client and Slack, with workspace governance handled through the integration approval process.

_Full upstream README: https://allmcps.com/mcp/slack-mcp/readme_