Skip to main content
Back to the Slack MCP server

MCP Gateway · Claude Cowork

Slack icon

Connect Slack to Claude Cowork

Cowork can take a longer Slack task from start to finish, such as reading weeks of discussion, writing it up and sharing the result. Slack reaches Cowork as a plugin synced from your organization's marketplace, and Speakeasy checks each prompt and ties every session to the person running it.

Category
Communication
Tools
13
Authentication
OAuth
Claude Cowork
Cowork tab in Claude Desktop

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 Cowork 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. Claude Cowork connects to the Slack server's own URL, and the server's authorization decides who can connect and which tools they can call.

  3. 03

    Connect Claude Cowork

    Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork.

    New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.

    Add the importing admin's GitHub username as a marketplace collaborator and accept the invite. Only that admin needs it.

    In Claude Organization settings > Plugins & skills, select Add > Sync from GitHub and pick the organization's plugin repository. The Claude GitHub App must be installed on it.

    Mark the observability plugin Required, and set the plugin that carries this server to Available to install or Installed by default.

    In the Cowork tab's Monitoring settings, set the OTLP endpoint, protocol and headers.

  4. 04

    Sign in and use Slack from Claude Cowork

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

Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.

Use cases

What Claude Cowork users do with Slack

Turn a project channel into a report

Cowork reads the project channel and its longest threads, writes a status report with decisions and blockers, and saves it as a Slack canvas for stakeholders.

slack_read_channelslack_read_threadslack_create_canvas

Keep a running FAQ canvas current

Cowork reads an existing FAQ canvas, searches public channels for questions people asked since the last update, and appends the new answers to the canvas.

slack_read_canvasslack_search_publicslack_update_canvas

Prepare follow-ups after planning

After a planning meeting, Cowork looks up the owner of each action item and saves a draft follow-up in the team channel naming each one, for you to review and send.

slack_search_usersslack_send_message_draft

Tools

13 tools

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

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

Prompt blocking

Claude Cowork

Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.

Session telemetry

Claude Cowork

Cowork's OTLP export ties sessions to people and feeds observability.

Anthropic inference hooks

Claude Cowork

On Claude Enterprise, prompts can be checked before inference (beta).

  • Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
  • Personal Claude accounts can't be governed in Cowork.

Questions

Frequently asked questions

Do Cowork users need a GitHub invite to get the Slack plugin?
No. Members who receive plugins through Cowork don't need a GitHub invitation. Only the importing admin is added as a marketplace collaborator.
Can personal Claude accounts use Slack in Cowork through Speakeasy?
No. Personal Claude accounts can't be governed in Cowork. Neither the device agent nor MDM reaches Cowork, so the Claude-side plugin setup always applies.
How do Claude Cowork users get Slack?
An admin adds Slack from the Speakeasy MCP Catalog and grants access by team or role. Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork. Each person then sees only the Slack tools their access allows.
Are Slack calls from Claude Cowork 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.