How to Connect Claude to Slack with MCP

Connecting Claude to Slack lets Claude search your workspace's channels, threads, files and people, and answer questions from what your team has discussed. Slack's connector can also send messages and create canvases. Slack hosts the MCP server, and Slack lists Claude.ai as a partner client.

Checked against: Slack's MCP server docs and Claude's Slack integration docs on 28 October 2026. eSEOspace did not run these steps; menus can change, so follow the vendor's page if it differs.

Before you start

• A Claude Team or Enterprise plan. Claude's Slack page says the connector is available on those plans.
• The Claude in Slack app, approved by a Slack admin. Claude's docs say to install the app before enabling the connector. Slack's developer docs add that workspace admins approve and manage MCP client integrations.
• A Claude Owner. The Owner enables the connector for your organization once.
• Your own Slack account. Claude acts with your Slack permissions, so it only sees what you can see.

Steps

Slack admin: approve the Claude app

Claude's docs give these steps for a Slack admin:

1. Open the Claude app's listing in the Slack App Marketplace.
2. Select Add to Slack, then review and approve the app for your organization.
3. Deploy the app org-wide or to specific workspaces.

If your Slack requires admin approval and you aren't an admin, you see Request to install instead.

Claude Owner: enable the connector

1. In claude.ai, go to Organization settings > Connectors and enable the Slack connector. Claude's directory listing shows it as made by Slack, with this connector URL:

https://mcp.slack.com/mcp

Each member: connect your account

1. Go to Customize > Connectors in claude.ai.
2. Find Slack and select Connect. Approve the Slack consent screen.
3. When it works, the Connect button changes to Disconnect.
4. In a chat, select + at the lower left of the message box, select Connectors, and turn on Slack.

Check that it works

Claude's directory listing names these tools: slack_send_message, slack_search_public_and_private, slack_search_users, slack_search_channels, slack_search_public, slack_read_channel, slack_read_thread, slack_create_canvas, slack_update_canvas, slack_read_canvas and slack_read_user_profile.

Example prompts

These two come from Claude's Slack docs:

• "What did the team decide about the launch date in #product-planning last week?"
• "Find the thread about the vendor contract renewal and summarize it."

A third to test canvases:

• "Create a canvas that summarizes this week's decisions in #product-planning."

Permissions and safety

• It acts as you. Slack's server uses user tokens. Claude reads channels and DMs you can access and sends messages under your name.
• Writes are real. Sending a message needs the chat:write scope, and canvases need canvases:write. Slack's developer docs list these scopes for each tool.
• Set tool permissions in Claude. On the connector's page under Customize > Connectors, Tool permissions lets you choose Always allow, Needs approval or Blocked for each group of tools. Claude's docs say Team and Enterprise Owners can restrict actions org-wide, for example allowing reads while blocking writes.
• Admin oversight. Slack says admins manage MCP clients through its standard app approval process, and MCP activity appears in Slack's audit logs.
• Okta-managed access. Slack's identity provider guide covers Enterprise-Managed Authorization for Slack Enterprise+ customers who use Okta and Claude Team or Enterprise. Setup needs a Slack Org Owner, an Okta Super Admin and a Claude Owner, and it keeps members on their work accounts.
• Mixing servers. Slack's docs ask you to think carefully before connecting other MCP servers at the same time, since Slack data becomes context for them too.

Slack messages come from many people and can hide instructions aimed at an AI. Read MCP prompt injection and cross-server data leakage, and see the MCP Security Center for more.

If it doesn't work

• You see Request to install. Your Slack needs admin approval. Ask a Slack admin to approve the Claude app, then connect.
• Slack isn't in your connector list. Check that you are on a Team or Enterprise plan and that an Owner has enabled the connector under Organization settings > Connectors.
• Rate limits. Slack says MCP tools follow the same rate limits as its Web API, set per tool. Searching and sending messages have special limits.
• IP restrictions. If the Slack app has allowed IP ranges set, Slack rejects MCP calls from addresses outside them.

Neither page lists other error messages. If none of these apply, disconnect under Customize > Connectors and connect again.

Next step

For the full scope list and rate limits, read the Slack MCP server profile. To connect Claude to other tools, browse the MCP connection guides. If you are rolling Claude out to a team, our lesson on MCP for teams covers approvals and shared settings.

Frequently asked questions