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.
1. Add your Slack workspaces to Carly
- Sign in at carlyassistant.com.
- Open carlyassistant.com/integrations.
- Find Slack, click Connect, and authorize the workspace.
- Click Connect again for the next one, and keep going for as many workspaces as you want.
Each workspace keeps its own authorization, and Carly reaches only the channels that account can already open.
Carly connects to thousands of apps, so while you are on that page you can add your inboxes, calendars, CRM, and anything else you want Grok to reach through the same connector.
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.
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.
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.
Almost every third-party claim of a live Slack connector traces to one source, worth naming so you can recognise it.
Grok Automations are real, and it is worth being fair about how far they reach.
| 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 |
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.
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.
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."
