Skip to main content
Back to the Slack MCP server

MCP Gateway · Cursor

Slack icon

Connect Slack to Cursor

Cursor users can bring the Slack discussion behind a feature into the editor and write decisions back for the team. The Speakeasy MCP Gateway handles sign-in, applies per-role rules to each Slack tool, and records which developer made every call, using the email each Cursor hook event carries.

Category
Communication
Tools
13
Authentication
OAuth
Cursor
Editor and terminal

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 Cursor 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 Cursor

    Add the gateway to Cursor in one click from the Organization Gateway page.

    On the Organization Gateway page in Speakeasy, choose Cursor under Install.

    Click Add to Cursor to add the gateway to Cursor's MCP settings, then sign in when Cursor prompts you.

  4. 04

    Sign in and use Slack from Cursor

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

For a whole team, a Cursor team admin imports the plugin marketplace under Settings > Plugins > Import and turns on Serve Marketplace From Cursor, so members install without GitHub access.

Use cases

What Cursor users do with Slack

Read the spec from a canvas

When requirements live in a Slack canvas, Cursor reads its markdown content and keeps it beside the component you're building, so the implementation follows what the team agreed.

slack_read_canvas

Record decisions in the design canvas

After you settle an approach in the editor, Cursor appends the decision and the files it touched to the existing canvas instead of replacing what others wrote.

slack_update_canvas

Catch up on a channel before editing

Cursor reads the newest messages in the team's channel first, so you notice recent reports about the module you're about to modify before you change it.

slack_read_channel

Tools

13 tools

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

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

Prompt and tool-call blocking

Cursor

Cursor hooks send each prompt and tool call to Speakeasy, which allows or denies it before Cursor runs it, and fail closed.

User attribution

Cursor

Every Cursor hook event carries the user's email.

Budgets

Cursor

Spend limits can block Cursor traffic once a budget is reached. Connect the Cursor Admin API for dollar spend.

Device agent and MDM

Cursor

The device agent installs the marketplace and plugins and reapplies them every minute.

  • Cursor Cloud agents need a checked-in .cursor/hooks.json. Session and MCP-specific hooks don't run there.
  • After a plugin update, members run Developer: Reload Window.

Questions

Frequently asked questions

Can Speakeasy block a Slack message Cursor is about to send?
Yes. Cursor hooks send each tool call to Speakeasy, which allows or denies it before Cursor runs it. The hooks fail closed.
Do developers need to reload Cursor after the Slack plugin changes?
Yes. After a plugin update, members run Developer: Reload Window. On managed laptops, the device agent installs the marketplace and plugins and reapplies them every minute.
How do Cursor users get Slack?
An admin adds Slack from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway to Cursor in one click from the Organization Gateway page. Each person then sees only the Slack tools their access allows.
Are Slack calls from Cursor 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.