Slack MCP server

Slack × Claude

Use the Slack MCP server
in Claude

Search messages, post to channels, and read your Slack workspace from your AI. This guide connects Slack to Claude (claude.ai and the Claude desktop app) 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 Claude

Claude adds MCP servers via custom connectors in Settings. The gateway route takes about two minutes:

  1. Create a free gate gateway and connect Slack to it from the verified directory (one click — note: Slack currently restricts third-party sign-ins, so use the API-key path if the vendor offers one).
  2. Open claude.ai → Settings → Connectors and click 'Add custom connector'.
  3. Name it 'gate' and paste your gateway URL, then approve the authorization.
  4. Ask Claude something Slack can answer — the call runs through your gateway, with your rules applied and logged.

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 Code, ChatGPT, Cursor, 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 Claude 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 Code · Slack in ChatGPT · Slack in Cursor · Slack in VS Code