By Goptin · Updated 2026-11-05

Slack MCP servers compared

There are now several ways to give Claude, Cursor or Codex access to Slack. They differ in who hosts them, what tokens they use, whether your admin has to approve them, and whether one setup can cover more than one workspace.

We build one of these (Goptin), so read this with that in mind — we have tried to be fair, and we say where the others are the better fit.

Slack's hosted MCP server

Slack runs an official server at mcp.slack.com/mcp with guides for Claude and Cursor. Sign-in is OAuth, access follows your Slack permissions, and workspace admins approve and audit which clients connect.

Best for: one workspace, an admin who is happy to approve it, and a Slack-only workflow. Watch out for: each sign-in covers one workspace; multi-workspace support in the Claude connector is an open request (anthropics/claude-code#44243).

korotovsky/slack-mcp-server (open source)

A popular MIT-licensed server you run yourself over stdio, SSE or HTTP. It accepts a user OAuth token (xoxp), a bot token (xoxb, limited to invited channels) or browser session tokens (xoxc/xoxd). Posting is disabled by default and can be enabled per channel.

Best for: developers who want full control and are comfortable managing tokens. Watch out for: browser session tokens may conflict with your company's Slack policy; each running instance is configured with one workspace's tokens.

Composio

A hosted integration platform with hundreds of toolkits, Slack included. It handles OAuth for you and lets you set up several Slack MCP instances.

Best for: developers building agents that need many SaaS tools. Watch out for: it is a general toolkit platform — you assemble the inbox and cross-account workflow yourself.

Goptin

A unified work inbox that also exposes one Streamable HTTP MCP server. You connect each Slack workspace once, plus Microsoft Teams, Google Chat, Jira and ClickUp, and every tool takes an account argument — "read Slack job A, post in Slack job B" is one prompt. A morning digest and task list sit on top.

Best for: people who work across several workspaces or companies. Watch out for: it is a paid product after the 14-day trial; Teams work tenants need admin consent until Microsoft publisher verification completes; Google Chat still shows Google's unverified-app screen.

How to choose

1
Count your workspaces
One workspace → Slack's hosted server is the simplest. Two or more → pick a server that holds several accounts in one tool set.
2
Check your admin policy
If your workspace restricts apps, every option needs admin approval. Avoid browser session tokens where company policy forbids them.
3
List the other apps you need
Slack only → any option works. Slack plus Teams, Google Chat or Jira in the same prompt → a multi-app server saves you one server per app.
4
Decide who hosts it
Self-hosted open source gives you control; hosted options remove token refresh and uptime chores.

At a glance

	Slack hosted MCP	korotovsky (OSS)	Composio	Goptin
Hosting	Slack	You	Composio	Goptin
Auth	OAuth	User, bot or browser tokens	OAuth (managed)	OAuth per account + personal bearer token
Several workspaces	One per sign-in	One per instance	Several instances	All in one tool set
Other apps	Slack only	Slack only	Hundreds of toolkits	Teams, Google Chat, Jira, ClickUp
Sending messages	Yes	Off by default	Yes	Yes, with a show-first instruction
Price	Included with Slack	Free	Free tier + paid	14-day trial, then paid

FAQ

What is the best Slack MCP server for Claude Code?

For a single workspace, Slack's hosted server is the easiest. For several workspaces, or Slack together with Teams, Google Chat and Jira, a multi-account server such as Goptin avoids registering one server per account.

Can one Slack MCP server use two workspaces?

Slack's hosted server and the open-source korotovsky server cover one workspace per sign-in or instance. Composio lets you create several instances; Goptin puts all connected workspaces behind one tool set with an account argument.

Is it safe to use browser session tokens (xoxc/xoxd)?

They act as your logged-in browser session and can violate company policy. Prefer OAuth-based options for work workspaces.

Which ones work in Cursor and Codex?

All four can be used from Cursor. Goptin and the self-hosted server also work in Codex CLI, Gemini CLI, VS Code and Windsurf through a plain URL and header config.

Try Goptin with your workspaces — free for 14 days →

No card needed. Facts about other products were checked in November 2026 — tell us if something changed.