MCP Gateway · Claude
Connect Slack to Claude
Claude can read the channels and threads your team already works in and turn them into summaries, replies and updates. Through the Speakeasy MCP Gateway, each person connects once from Customize > Connectors, authorizes with their own Slack account, and sees only the Slack tools their role allows.
- Category
- Communication
- Tools
- 13
- Authentication
- OAuth
- Claude
- Web, desktop and mobile
Behind the MCP Gateway
Run Slack MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Slack call inspected and logged.
Before you start
What Slack needs first
A user who can create or manage a Slack app, plus any required workspace-admin approval does the Slack side of the setup.
- You need permission to create or manage the app and any required workspace-admin approval.
- Only internal apps and Slack Marketplace apps can use the MCP server.
- Each user authorizes with their own Slack account. No bot token or API key is used.
In Slack
- Create the app from Speakeasy's prefilled manifest link, or enable MCP on an existing app.
- Remove any user scopes you do not want to grant.
- Copy the app's client credentials.
Set up
Add Slack to Claude in 4 steps
- 01
Add Slack from the catalog
An admin finds Slack in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.
Slack uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.
Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.
- 02
Choose who can use Slack
Give teams the
mcp:connectscope on the Slack server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Slack to their gateway on the next call, and removing it takes it away. - 03
Connect Claude
Add the gateway URL as a custom connector, then connect it from Customize > Connectors.
On Team and Enterprise plans, an Owner opens Organization settings > Connectors, chooses Add > Custom > Web and pastes the gateway URL.
Each person opens Customize > Connectors and clicks Connect to sign in.
On Pro and Max plans, each person adds it themselves under Customize > Connectors, with + Add > Add custom connector.
- 04
Sign in and use Slack from Claude
The first time Claude connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
Slack needs its own OAuth grant, so each person connects it once. Until they do, Slack calls fail while the rest of the gateway keeps working.
From then on, Slack's tools appear in Claude, limited to what the person's access allows, and every call lands in the gateway's tool logs.
No client ID or secret is needed: the gateway's sign-in handles client registration. Each person only sees the servers their role can reach.
Use cases
What Claude users do with Slack
Catch up after time away
Ask Claude to go through the latest messages in your project channels and summarize the decisions, open questions and anything addressed to you while you were out.
Find the right person to ask
Search Slack by department, role or title to find who handles a topic, then check their profile for timezone and status before you reach out.
Draft a reply for review
Claude writes an answer to a question in the support channel and saves it to your Drafts & Sent in Slack, so you can edit it before it goes out.
Tools
13 tools
Each Slack tool can be allowed or denied per team and role at the MCP Gateway before Claude sees it.
slack_send_message
Sends a message to a Slack channel or user. To DM a user, use their user_id as channel_id. Return the message link to the user.
slack_schedule_message
Schedules a message for future delivery to a Slack channel. Does NOT send immediately — use slack_send_message for that.
slack_create_canvas
Creates a Slack Canvas document from Canvas-flavored Markdown content. Return the canvas link to the user. Not available on free teams.
slack_update_canvas
Updates an existing Slack Canvas document with markdown content. Supports appending, prepending, or replacing content.
slack_search_public
Searches for messages, files in public Slack channels ONLY.
slack_search_public_and_private
Searches for messages, files in ALL Slack channels, including public channels, private channels, DMs, and group DMs.
Control
What Speakeasy can see and stop in Claude
The gateway covers every client the same way. The rest depends on what Claude exposes to Speakeasy.
Tool logs
Gateway
Every Slack call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Slack tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Slack can reject a tool request before it reaches the server, or withhold a result from Claude. MCP-scoped policies are enabled per organization.
Anthropic inference hooks
Claude
On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.
Conversation import
Claude
Claude conversations can be imported through Anthropic's Compliance API for review after the fact.
- Custom connectors need a Claude plan that supports them.
- Budgets don't cover Claude web and desktop usage.
Questions
Frequently asked questions
Which Claude plans can connect Slack through Speakeasy?
Can Claude search my private Slack channels?
How do Claude users get Slack?
Are Slack calls from Claude logged?
Connect more