How to Connect Multiple Slack Workspaces to Grok
The consumer Grok app has no Slack connector. Not among the built-ins, and not in the catalog as far as anyone outside xAI can establish. The only route Grok itself offers is a custom MCP connector, and that route is blocked on Slack’s side too. So the multi-workspace question collapses a level: there is no first workspace to hold, let alone a second. Carly holds your Gmail and Outlook mailboxes and every calendar on both sides in the same place.
Worth knowing before you spend an afternoon on it, because search results on this exact question are unusually wrong. More on why below.
One orientation note. “Grok” now names three products and this page is about the consumer assistant. Grok for Slack is a separate Slack app you install into a workspace, covered in connecting multiple Slack workspaces to Grok Bot. Grok Bot is the newer teammate product, and xAI’s own FAQ says it “is not the same as Grok on grok.com or the Grok mobile apps”. Installing Grok for Slack does not give grok.com a Slack connector. No xAI document states that either way, so treat it as an inference, but it is the wrong assumption people most often arrive with.
Seven built-in connectors, and Slack is not one of them
xAI’s connector documentation lists the built-in set as Gmail and Google Calendar, Google Drive, OneDrive, Outlook Mail and Calendar, Microsoft Teams, SharePoint and Salesforce. Each of the seven has its own documentation page. There is no Slack page, no Slack row, and no Slack mention anywhere in the consumer Grok docs. xAI’s May 2026 launch announcement for connectors named SharePoint, Outlook, OneDrive, Google Workspace, Notion, GitHub and Linear plus bring-your-own MCP, without mentioning Slack once, and nothing has been announced since. A tour of the whole set is in our Grok connectors overview.
One limit on that evidence, stated precisely. xAI’s docs only say “browse the full catalog at grok.com/connectors”, and signed out that page shows a heading and a sign-in button, so xAI is silent on what the full catalog contains. The best corroboration is third party: a community directory updated on 12 August 2026 captured the logged-in picker at 28 tiles, including Stripe, Wix, Calendly, Figma, HubSpot and BigQuery, and reported the only messaging tile as Microsoft Teams. That is a community capture rather than vendor documentation. It agrees with the docs, which is the most you can say.
Grok’s messaging connector is Teams, which makes the gap easy to see
Reading the Microsoft Teams documentation is the fastest way to see what a real Slack connector would have given you. xAI names the capabilities individually: search messages across channels and chats by keyword, read channel messages including threaded replies, reactions and mentions, read chat messages from one-to-one and group chats, send channel messages and reply to threads, send chat messages, create chats, browse teams and channels, and view team and channel members.
Those are the verbs, and the write side is documented rather than merely permitted by a scope, which is a distinction worth respecting here. The Teams page also carries the constraint that matters most for the multi-account question: Grok “can only access teams, channels, and chats that the signed-in user already has access to”. The Outlook page says the same about mail, limiting Grok to the signed-in user’s mailbox.
For Slack there is no equivalent list, because there is no connector to document.
Where “Grok can post to Slack” comes from
Almost every third-party claim of a live Slack connector traces to one source, worth naming so you can recognise it.
In July 2025 an article republished an internal “Grok Tools Documentation” table with a Slack tier: Slack List Channels, Get Channel By Name, Get Conversation History, Get Thread Replies, List Users, Get User Profile, Get Conversation Info, List Conversation Members, Get User Info, Search Messages, with a broader “Slack (All)” tier adding Post Message, Reply To Thread, Add Reaction, and Join and Leave Conversation. The same article said the Slack and Calendar connectors were “still gated to testers”.
Google Calendar from that leak shipped about ten months later. Slack never did. A capability list resembling Slack List Channels or Slack Post Message is leak provenance, not shipped product. A related trap: a web search on this question will confidently describe a live connector, quote something about listing the first 50 channels in a workspace, and cite a docs URL like connectors/catalog.md. That URL returns a 404 and no catalog page exists in the documentation.
Nothing in Grok fires when a Slack message arrives
Grok Automations are real, and it is worth being fair about how far they reach.
Since July 2026 Grok can start work on its own two ways: a schedule, or an incoming email that matches your filters. Email is the only event it watches. The connectors it has to Salesforce, Teams, SharePoint, and the rest never fire anything — they wait to be asked inside a conversation.
Applied to Slack that leaves one indirect path, and it is thin. Slack’s own email notifications land in a mailbox you have connected, and an email trigger can match them. It inherits Slack’s notification delay and per-channel settings, matches only sender, recipient or subject rather than the message body or attachments, needs SuperGrok, and cannot post anything back into Slack. The full trigger picture is in Grok Automations.
Sort your case
| What you want | Native path in the Grok app |
|---|---|
| One Slack workspace connected | No connector exists |
| Two or more Slack workspaces | Not applicable, there is no first one |
| Two accounts of any one connector | Not documented either way |
| A messaging connector at all | Yes, Microsoft Teams, read and send |
| Slack via your own MCP server | Custom connector, you build and host it |
| Slack’s hosted MCP server | Documented on both ends, and they do not meet |
| Reacting to a Slack message | No, unless a Slack notification email matches a filter |
Slack’s own MCP server exists, and Grok cannot use it
On paper this looks like the answer. Slack ships a hosted MCP server whose documented tools cover searching messages, files, users and channels, sending and drafting messages, reading channels and threads, creating conversations, reactions and canvases. Grok accepts custom MCP connectors. Two documented halves.
They do not fit. Slack’s documentation states that MCP clients “must be backed by a registered Slack app with a fixed app ID” and must hardcode that app ID, and that “only apps published in the Slack Marketplace and internal apps can use MCP at this time; unlisted apps are prohibited from using MCP”. It also rules out SSE-based connections and Dynamic Client Registration. The no-code clients Slack names are Claude.ai, Claude Code, Perplexity and Cursor. Grok is absent, and Grok for Slack is not in the Slack Marketplace, which is the other half of the requirement.
So pasting Slack’s hosted MCP URL into Grok’s Custom box is expected to fail authentication. Treat that as a strongly evidenced inference rather than a tested result: both vendors are explicit in their own docs, and nobody has published the combination failing. Test it in five minutes if you want certainty, and do not build a workflow on the assumption it will work.
What Slack Connect does not solve
Slack Connect shares a channel between two organizations inside Slack, so people reach for it here. It changes who can see a channel within Slack, and it creates nothing on Grok’s side, so there is no connector for a shared channel to feed. Per-workspace switching is not an answer either, because there is nothing to switch between.
1. Connect every workspace to Carly
- Sign in at carlyassistant.com.
- Open carlyassistant.com/integrations.
- Find Slack and click Connect.
- Authorize the first workspace, checking the name on Slack’s consent screen.
- Return to the integrations page and click Connect on Slack again for the next workspace.
- Repeat for every remaining workspace, including client workspaces you joined as a guest.
Each workspace keeps its own authorization, and Carly reaches only the channels that account can already open.
2. Add Carly to Grok
- Go to grok.com/connectors.
- Click New Connector, then select Custom.
- Enter
https://carlyassistant.com/mcp/. - Complete the authentication step.
- Sign in to the Carly account holding the connections above.
Grok discovers the tools Carly exposes and offers them in conversation alongside its built-in connectors. On Grok Business and Enterprise a team admin provisions connectors in the cloud console first.
3. Test read-only, then across workspaces
One workspace per prompt until you trust the routing:
In the Databricks workspace, list the five most recent messages in #project-updates with sender and timestamp. Do not post anything.
Then the question no per-workspace setup answers:
Search my workspace, the Databricks workspace and the Cisco partner workspace for “scope change” in the last 14 days. Show the source workspace and channel on every row.
Reuse a routing prompt once that is reliable:
Treat my own Slack as Internal, the Databricks workspace as Client and the Cisco partner Slack as Partner. Name the source workspace on every result. Never post in Client or Partner without showing me the draft first.
Grok versus Carly on Slack
| Need | Grok app | Carly |
|---|---|---|
| A Slack connector at all | None documented | Yes |
| Hold several Slack workspaces | Nothing to hold | Yes, one authorization each |
| Read channels and threads | Only via your own MCP server | Yes |
| Post a message or reply in a thread | Only via your own MCP server | Yes |
| A documented messaging connector | Yes, Microsoft Teams | Yes |
| Start when a Slack message arrives | No, notification email only | Yes |
| Setup you do not host yourself | No, custom MCP is yours to run | Yes |
Give Grok its due on the rows where it is strong. The Teams connector is documented verb by verb, covers sending as well as reading, and is bounded honestly by the signed-in user’s own access. Email triggers are a real step past assistants that only run on a clock, and xAI shipped them while most rivals had nothing. If your company runs on Teams and Outlook, Grok is a reasonable pick and Slack is not your problem.
Carly answers the shape Grok has no path for. Slack is a native connector, you authorize each workspace yourself, and several sit side by side on one account, so one question can span your own Slack, a client’s and a partner’s with the source named on every row. It acts when the message arrives rather than waiting to be asked, and none of it requires you to host a server or keep a tunnel URL alive. If your case is stranger than the connector list allows, the API path is available and worth a conversation.
Free Zapier-style workflows; AI agents from $35/month. Connect it on the integrations page, or start with Slack.
Quick fixes
| Problem | Fix |
|---|---|
| A blog or AI answer says Grok has a Slack connector | It is almost certainly the July 2025 internal tools leak; the docs list seven built-ins and Slack is not among them |
| Slack’s MCP server URL will not authenticate in Grok | Slack requires a registered app with a fixed app ID, Marketplace-listed or internal, and Grok is not on its client list |
| You installed Grok for Slack and grok.com still cannot see Slack | Different products; the Slack app does not create a connector on grok.com |
| A workspace is missing from Carly | Reconnect it from the integrations page and confirm the workspace name on Slack’s consent screen |
| Grok rejected your MCP URL outright | localhost and private-range addresses are rejected; the server must be reachable on the public internet |
| Nothing happens when a Slack message arrives | There is no Slack trigger; a Slack notification email matched by sender or subject is the nearest thing, on SuperGrok |
Frequently asked questions
Does Grok work with Slack?
Not the consumer app at grok.com. Its documented built-ins are Gmail and Google Calendar, Google Drive, OneDrive, Outlook Mail and Calendar, Microsoft Teams, SharePoint and Salesforce, with no Slack page anywhere in xAI’s docs. Separately, Grok for Slack is an unlisted Slack app you install into a workspace, and Grok Bot can wake a routine on a Slack message. Different products.
Can I connect two Slack workspaces to Grok?
No, and not because of a two-account limit. There is no Slack connector to connect once. Whether Grok holds two accounts of any single connector is undocumented, and the nearest signals lean singular: both the Teams and Outlook pages limit access to the signed-in user.
Can I use Slack’s MCP server as a custom connector in Grok?
It is expected to fail. Slack requires MCP clients to be backed by a registered Slack app with a hardcoded fixed app ID, and permits only Marketplace-published or internal apps to use MCP. Grok is not among the clients Slack names, though nobody has published the combination being tested.
Why do search results say Grok has a Slack integration?
They are recycling the July 2025 article that republished an internal Grok tools table containing Slack verbs, sometimes blended with a community capture of the connector picker. Google Calendar from that leak shipped roughly ten months later. Slack never shipped, and the docs URL those answers cite does not exist.
Related: Multiple Slack workspaces in Grok Bot · Grok connectors · Grok Automations · MCP servers · Best AI assistants for Slack · Carly’s Slack integration
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
