Skip to main content
Back to the Slack MCP server

MCP Gateway · Claude Code

Slack icon

Connect Slack to Claude Code

Claude Code can read the Slack thread where a bug was reported and post an update when the fix is ready, without leaving the terminal. The Speakeasy MCP Gateway gives it one governed URL for Slack, each developer authorizes with their own Slack account, and every message Claude Code reads or sends is logged against their name.

Category
Communication
Tools
13
Authentication
OAuth
Claude Code
CLI

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.

Deploy on MCP Gateway

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

  1. Create the app from Speakeasy's prefilled manifest link, or enable MCP on an existing app.
  2. Remove any user scopes you do not want to grant.
  3. Copy the app's client credentials.
Full Slack setup guide in the docs

Set up

Add Slack to Claude Code in 4 steps

  1. 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.

  2. 02

    Choose who can use Slack

    Give teams the mcp:connect scope 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.

  3. 03

    Connect Claude Code

    Add the organization gateway as an HTTP MCP server, then authenticate from /mcp.

    Run the command below with your organization gateway URL.

    Open /mcp in Claude Code and choose Authenticate to sign in.

    claude mcp add --transport http --scope user \
      'speakeasy' \
      'https://<organization host>/mcp/gateway/<organization slug>'
  4. 04

    Sign in and use Slack from Claude Code

    The first time Claude Code 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 Code, limited to what the person's access allows, and every call lands in the gateway's tool logs.

To roll it out to a whole team, publish the server in a plugin and register the plugin marketplace in Claude Code's managed settings, so every member gets it without running the command. The device agent can also write and reapply these settings on each laptop.

Use cases

What Claude Code users do with Slack

Pull the bug report thread

Paste a channel name or link and Claude Code reads the whole thread, parent message and replies, so the reproduction steps people described sit next to the code you're changing.

slack_search_channelsslack_read_thread

Post a deploy note to the team

Once a release script finishes, Claude Code sends a short message to the team channel saying what shipped, then hands you the message link so you can follow replies.

slack_send_message

Write the postmortem as a canvas

After an incident fix, Claude Code creates a Slack canvas with the timeline, the root cause and the commits involved, and returns the canvas link to share with the team.

slack_create_canvas

Tools

13 tools

Each Slack tool can be allowed or denied per team and role at the MCP Gateway before Claude Code 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.

See all 13 tools

Control

What Speakeasy can see and stop in Claude Code

The gateway covers every client the same way. The rest depends on what Claude Code 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 Code. MCP-scoped policies are enabled per organization.

Prompt and tool-call blocking

Claude Code

Agent hooks send each prompt and tool call to Speakeasy, which allows or denies it before Claude Code runs it.

User attribution

Claude Code

Claude Code's OpenTelemetry exporter ties each session to a named person. Without it, activity can't be attributed.

Budgets

Claude Code

Spend limits can block Claude Code traffic once a budget is reached.

Device agent and MDM

Claude Code

The device agent installs the marketplace, plugin and telemetry settings and reapplies them every minute. It deploys through MDM.

Anthropic inference hooks

Claude Code

On Claude Enterprise, prompts can be checked before inference with nothing installed on the device (beta).

  • Claude Code on the web doesn't use the laptop setup. It needs the device agent in a shared Anthropic-hosted environment.
  • Plugin marketplace URLs for Claude Code carry an access token, so share install snippets only through a private channel.

Questions

Frequently asked questions

Can Claude Code post to Slack without my approval?
Agent hooks send each tool call to Speakeasy, which allows or denies it before Claude Code runs it. An admin can also deny slack_send_message for a role at the gateway and leave the read tools on.
Does Claude Code need a Slack bot token?
No. Each developer authorizes with their own Slack account, and the setup uses no bot token or personal API key. Claude Code reaches Slack through the gateway and never holds a Slack credential.
How do Claude Code users get Slack?
An admin adds Slack from the Speakeasy MCP Catalog and grants access by team or role. Add the organization gateway as an HTTP MCP server, then authenticate from /mcp. Each person then sees only the Slack tools their access allows.
Are Slack calls from Claude Code logged?
Yes. Slack calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

Slack in other clients

AI everywhere.

Control here.