By Goptin · Updated 2026-11-03
How to connect multiple Slack workspaces to Claude
You work in two Slack workspaces — your company and a client, or two jobs — and you want Claude to read and answer in both. The built-in Slack connector signs in to one workspace per Claude account, so the second one is out of reach.
This guide shows the options, and the one-server setup we use ourselves: connect every workspace once in Goptin, add a single MCP server to Claude, and ask for "Slack job B" by name.
Why the second Slack workspace doesn't work
A Slack connector or Slack MCP server authorizes against a single workspace. Adding the same connector again usually replaces the first sign-in instead of adding a second one, and there is an open request for multi-workspace support in the Claude Code repository (anthropics/claude-code#44243).
The same thing happens with two Google Chat accounts, two Jira sites or two ClickUp workspaces.
Your options
1. Register the Slack server twice (Claude Code only). Add the Slack MCP server under two names such as slack-a and slack-b and authorize each one into a different workspace. It works, but you repeat it for every app and every account, each server has its own login to keep alive, and Claude has to guess which copy to call.
2. One MCP server that knows all your accounts. A router server holds a connection per workspace and exposes them as one tool set. Every tool takes an account argument, so one prompt can read Slack job A and post in Slack job B. This is what Goptin does — and it also covers Microsoft Teams, Google Chat, Jira and ClickUp, with several accounts per app.
Set it up with Goptin (about 2 minutes)
- 1Connect each Slack workspace in GoptinStart the free trial at app.goptin.com and open Connections. Connect each Slack workspace (repeat for the second and third). Add Teams, Google Chat, Jira or ClickUp the same way.
- 2Create a personal tokenIn Settings → Integrations, create a token. It is shown once, stored only as a hash, and can be revoked at any time.
- 3Add the server to Claude CodeOne command. Use
--scope localinstead to enable it for a single project only.claude mcp add --transport http goptin https://app.goptin.com/mcp --scope user --header "Authorization: Bearer goptin_…"
- 4Ask Claude by account nameClaude calls
list_accounts, then reads and writes through the right workspace:"Summarize what I missed in Slack job A today, then post a short update in #dev on Slack job B."
Built-in connector vs. two servers vs. Goptin
| Built-in Slack connector | Slack server registered twice | Goptin MCP | |
|---|---|---|---|
| Slack workspaces | 1 | One per copy | As many as you connect |
| Other apps | Separate connectors | Separate servers each | Teams, Google Chat, Jira, ClickUp in the same server |
| Where it works | Claude apps | Claude Code | Claude Code, Claude Desktop, Cursor, VS Code, Codex, Gemini CLI, Windsurf |
| Pick the account | — | By server name | By account name in the prompt |
| Extras | — | — | Unified inbox, morning digest, tasks, ticket updates |
FAQ
Can Claude use two Slack workspaces at the same time?
Yes, through an MCP server that holds a connection per workspace. With Goptin every tool takes an account argument, so one prompt can read from Slack job A and post in Slack job B.
Does it work in Claude Desktop and Cursor?
Yes. Goptin is a standard Streamable HTTP MCP server with a bearer token: Claude Code, Cursor, VS Code (Copilot), Windsurf, Codex CLI and Gemini CLI connect directly, and Claude Desktop connects through mcp-remote. Ready-made configs are in Settings → Integrations.
Will Claude send Slack messages without asking?
No. The server tells the model to show you the exact text first, and Claude Code asks for permission before every tool call that sends a message or changes a ticket.
What else can it do besides Slack?
Read and search conversations across Teams, Google Chat, Jira and ClickUp, read the daily digest, manage your Goptin task list, and comment on or move Jira/ClickUp tickets.
How much does it cost?
The MCP server is included in every Goptin plan, including the 14-day free trial — no card required.
No card needed. Revoke the token any time in Settings → Integrations.