CommunicationPublic source

Slack MCP Server

Give your AI agents full Slack access — messages, threads, DMs, channels, canvases, reactions, and search. 27 tools over the Slack Web API with enterprise governance and audit-ready risk classification.

Open the source Read the official guide ↗

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

Provides slack capabilities through a typed MCP contract.

Architecture

How Slack MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

→

MCP client

Discovers schemas, sends calls, and receives typed content.

→

Slack MCP Server

Validates the request and owns 27 documented tool contracts.

→

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: ADK MCP SDK + rmcp

Slack MCP Server architecture diagram from its official repository

Tool catalog

What can an agent ask Slack MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

9 named tools shown from 27 documented tools

list_channels

List Slack channels the bot has access to

read only

get_channel_history

Get recent messages from a channel

read only

send_message

Send a message to a Slack channel or thread

external write

add_reaction

Add an emoji reaction to a message

external write

search_messages

Search messages across all channels

read only

list_users

List workspace users

read only

set_channel_topic

Set a channel's topic

external write

upload_file

Upload a text file to a channel

external write

get_user

Get user profile info by user ID

read only

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

5 read only4 external write

The registry manifest declares read only, external write tool risk classes.

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

The current README concentrates on its tool surface. Check the source and release notes before relying on optional MCP capabilities beyond tool discovery and invocation.

ADK MCP SDKrmcpRegistry manifest

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install

cargo install mcp-slack

MCP client configuration

channels:read        — list channels
channels:history     — read messages
channels:manage      — set topic
groups:read          — private channels
groups:history       — private channel messages
chat:write           — send messages
reactions:write      — add reactions
search:read          — search messages
users:read           — list/get users
files:write          — upload files
channels:join        — self-join channels (optional)

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Overview ↗README.md Architecture ↗docs/assets/architecture.svg Issues and support ↗github.com issues

Keep exploring