Slack Official MCP Server

Slack's official hosted MCP server connects approved clients and registered apps to workspace search, messages, files, canvases and lists.

Start with a source-backed summary

A useful first workflow is finding a decision in a named channel and summarizing the relevant thread with links. Supply the subject and date range. Ask the assistant to distinguish an agreed decision from a suggestion or a later correction.

An endpoint is not the whole setup

The documented Streamable HTTP endpoint is https://mcp.slack.com/mcp. Slack requires a fixed registered app identity, and the documentation restricts access to Marketplace-published apps and internal apps. A generic MCP URL pasted into an arbitrary client is not a complete integration.

Use a supported partner client or follow the app-registration and OAuth instructions. Workspace administrators can manage the client integration. Account access, granted scopes and app restrictions still determine which resources it can use.

Separate reading from sending

Search and thread retrieval are useful for research. Sending a message, changing a canvas or creating a list changes workspace content. Ask for a proposed message and its destination before applying that workflow. Rate limits apply to the associated Slack action.

Official hosted server versus the archived reference

The older Slack reference server lives in the MCP archived-server repository. It has a different local configuration and maintenance history. Do not copy its token variables or package command into a hosted OAuth setup.

Publisher documentation

Source 1