Slack MCP server

Slack × Cursor

Use the Slack MCP server
in Cursor

Search messages, post to channels, and read your Slack workspace from your AI. This guide connects Slack to Cursor (the AI code editor) through a governed gateway — one URL that also works in every other MCP client you use, with your rules and a full log attached.

Live-probed · Security-scanned · Note: Slack currently restricts third-party sign-ins — API-key path recommended

Setup: Slack in Cursor

Cursor adds MCP servers via MCP settings or install deep links. The gateway route takes about two minutes:

  1. Connect Slack to your free gate gateway from the verified directory.
  2. On your gate overview, click 'Add to Cursor' — Cursor opens and asks to install the gateway.
  3. Confirm and approve the sign-in.
  4. Slack's tools are now available to Cursor's agent, governed by your rules.

What to ask once it’s connected

Summarize #support since yesterday.
Find the thread where we decided on the pricing change.
Post these release notes to #general.
What did I miss while I was out?

Why route it through a gateway

One URL, every client

The same Slack connection works in Claude, Claude Code, ChatGPT, VS Code too — no per-client re-wiring.

Rules before regret

Allow, ask, or block every tool Slack exposes — reads can flow freely while writes require your approval.

Every call logged

A plain-language activity log of everything Cursor did with Slack — searchable, exportable, auditable.

Scanned and probed

Slack passed a live handshake probe and a security scan before listing — and drift detection watches it after you connect.

Also available: Slack in Claude · Slack in Claude Code · Slack in ChatGPT · Slack in VS Code