Connect Multiple Email Accounts to Grok Bot
Carly is what keeps several email accounts separable inside Grok Bot. Grok Bot itself will take as many mailboxes as you hand it, Gmail through Cursor’s Gmail plugin and Outlook through its browser, but every one of those logins is account-wide, on a single shared computer that all of your Bots can drive. Connect each mailbox to Carly instead and every account stays its own addressable identity, so one Grok Bot conversation can work in whichever inbox you name.
What one chat can do afterwards
- Search a personal Gmail and a work Outlook in the same question.
- Compare a thread in one company’s mailbox against another’s.
- Produce a morning briefing grouped by inbox.
- Draft or send from the exact address you choose.
- Label, move, flag, or archive in the correct account.
- Check several calendars for conflicts while writing to only one.
Nothing is merged. Each mailbox keeps its own credentials and stays individually addressable, so an instruction that names Client cannot quietly land in Main Company.
More sign-ins, one shared set of logins
Most assistants cap you at one mailbox per provider. Grok Bot has the opposite failure, and it is the more dangerous one, because it looks like it worked. Gmail arrives through Cursor’s Gmail plugin, which takes more than one Google account under separate labels. Outlook has no plugin at all, so it arrives as a browser login on the shared computer.
xAI’s documentation on the shared computer is blunt about the shape. “Every Bot on your account uses the same computer: Browser cookies and signed-in sessions are shared, Files are visible to every Bot, Command-line credentials are shared.” Separate screens let Bots work in parallel, but the docs state those screens are “not separate security boundaries.” Installed connectors get the same treatment: “Installed connectors are account-wide. Their availability is not isolated to one Bot.”
So three email sign-ins inside Grok Bot means three live logins on one cloud VM, reachable by every Bot you own. Installed connectors are account-wide, the Gmail plugin exposes one tool list for every account it holds, and there is no per-mailbox permission and no way to tell one Bot to handle the client inbox while another stays out of it. Spinning up a second Bot for the client work does not help, because the second Bot inherits the first one’s cookies.
Grok Bot routines run on a schedule, and they can also start from an event when that event arrives through a Cursor account integration, such as a Slack message or a GitHub notification. The docs qualify this with "where supported," and the list leans toward developer surfaces rather than the CRM, billing, and form events most businesses run on.
That is the gap Carly closes. Each Gmail or Outlook identity is its own authorized connection, so the accounts stay apart no matter which Bot picks up the task.
1. Give each mailbox a role
Using fictional addresses:
| Address | Role in Grok Bot |
|---|---|
fictional.imani.brannigan@gmail.com | Personal |
fictional.imani.brannigan@kroger.com | Main Company |
fictional.imani.brannigan@bunge.com | Client |
Names like Personal, Main Company, and Client read better in everyday requests than “Gmail 1” and “Outlook 2.” Keep the full address for anything that changes a mailbox.
2. Connect every mailbox to Carly
- Sign in at carlyassistant.com.
- Open carlyassistant.com/integrations.
- Find Gmail or Outlook and click Connect.
- Authorize the first account and confirm the address that comes back.
- Return to Carly’s integrations page and connect the next identity.
- Verify the full address after each authorization, then repeat until every mailbox is listed.
Mix providers freely. A second Gmail sits beside the first, and Outlook sits beside both.
Two provider quirks are worth knowing before you start. Google preselects your current login, so choose Use another account rather than the suggested profile. Microsoft is stickier still and will silently reuse whichever account the browser already holds, so sign out of the Microsoft session between accounts or use a separate browser profile. A managed Google Workspace or Microsoft 365 tenant may also route consent to an administrator, which is policy rather than a failure and is worth resolving before you connect the rest.
3. Add Carly to Grok Bot
- Find Plugins on the Grok Bot sidebar, or under Settings, which also opens with Cmd or Ctrl plus comma. On the mobile app, tap your avatar at the top left and select Plugins.
- Add Carly’s remote MCP server,
https://carlyassistant.com/mcp/. - Finish the authorization in the browser tab that opens.
- Sign in to the Carly account holding the mailboxes you connected above.
- Confirm Carly appears under Installed.
Cursor and xAI describe the same screen from two directions, which is why it is worth checking both places. Cursor’s guide says to “select Plugins on the sidebar, or follow an in-chat Connect card,” while xAI’s docs say connectors “are shown as Plugins in the current app” and route you through Settings → Plugins.
Grok Bot takes remote MCP servers rather than local ones, and Carly’s is hosted, so it qualifies. One thing can stop you outright: Grok Bot runs on your Cursor account, and Cursor’s MCP policy lets a team admin decide whether members may configure their own MCP servers at all. If your plugin list is locked to the marketplace, that setting is the reason, and an admin has to change it.
4. Keep Require Approval on anything that sends
- Open the Bot’s approval rules.
- Add a Require Approval rule for sending external email.
- Extend it to moves, deletions, and calendar changes.
Reads and searches then run freely while a send from a client tenant stops in front of you. An approval covers the proposed action only and does not reverse work already done, so the rule belongs in place before the first real task.
5. Test read-only, then route by address
Start with something harmless in each mailbox:
In
fictional.imani.brannigan@kroger.com, list the sender and subject of the five newest unread messages. Do not change anything.
Then cross the providers:
Search the Kroger and personal Gmail example accounts for “renewal” in the last 30 days. Include the full source address on every row.
Then pin a routing rule you can reuse:
Treat
fictional.imani.brannigan@gmail.comas Personal,fictional.imani.brannigan@kroger.comas Main Company, andfictional.imani.brannigan@bunge.comas Client. Always state the target address before changing data. Wait for approval before sends, moves, deletes, labels, or calendar changes.
The one case where the shared browser holds up
If every mailbox is yours personally, carries no client data, and you run exactly one Bot, signing into the shared browser will get you through a read-only question today. What breaks is the second Bot. The moment you add one, or hand work to a teammate, or a client tenant lands in the mix, every cookie on that machine is already in scope, and there is no per-account setting to walk it back.
The shared browser next to Carly
| Need | Grok Bot’s plugin or shared browser | Carly plugin |
|---|---|---|
| Reach one mailbox | Yes | Yes |
| Hold several Gmail accounts | Yes, the plugin takes more than one login | Yes |
| Reach Outlook at all | Browser login only, no plugin exists | Yes |
| Give each account its own permissions | No, logins are account-wide behind one tool list | Yes, each is its own connection |
| Stop one Bot from reaching a client inbox | No, xAI rules this out explicitly | Yes, per connected account |
| Send from a named address | Whichever session the browser is in | Yes, with that account’s permissions |
| Say which account it acted in | Not reliably | On every action |
| Survive a handoff to another Bot | The next Bot inherits every login | Yes, routing stays by address |
Carly gives Grok Bot one account-aware toolset where the accounts stay apart, and Carly’s agents carry their own name, address, and memory, so a client can write to one directly and the work starts on arrival. Free Zapier-style workflows; AI agents from $35/month. Connect every inbox at carlyassistant.com.
Quick fixes
| Problem | Fix |
|---|---|
| A Bot acted in the wrong inbox | Name the full address in the instruction rather than the role |
| Two Bots need different access | Route through Carly and address accounts by name |
| The provider reused your signed-in account | Choose Use another account, or sign out of Microsoft between connections |
| A work account stalls at consent | A Workspace or Microsoft 365 administrator has to approve before authorization completes |
| Plugins will not let you add a server | Your Cursor team admin controls whether members may add their own MCP servers |
| Sends go out before you see them | Add a Require Approval rule for external email |
Frequently asked questions
Can Grok Bot connect to multiple email accounts?
Yes. Gmail comes through Cursor’s Gmail plugin, which takes more than one Google account, and Outlook comes as a signed-in browser session, since no Outlook plugin exists. Every one of those logins belongs to your account rather than to one Bot, so the mailboxes are reachable but not separable. Connecting each one to Carly is what makes them individually addressable.
Do separate Bots keep my inboxes apart?
No. xAI states that browser cookies, signed-in sessions, files, and command-line credentials are shared across every Bot on your account, and that the separate screens are not separate security boundaries.
Can I mix Gmail and Outlook?
Yes. Connect each identity to Carly whichever provider it belongs to, and one request can span both while still sending from the address you name.
Does connecting Carly give every Bot access?
Installed connectors in Grok Bot are account-wide, so plan access at the account level. What changes is that each mailbox inside Carly is a distinct authorized connection, so instructions name a target address instead of inheriting whatever the browser happens to be signed in to.
Will my admin need to approve anything?
Possibly twice. A managed Google Workspace or Microsoft 365 tenant may require administrator consent for the mailbox connection, and a Cursor team admin controls whether you may add your own MCP server to Grok Bot.
Related: Grok Bot · Connect multiple Gmail accounts to Grok Bot · Connect multiple Outlook accounts to Grok Bot · Connect multiple email accounts to ChatGPT · Connect multiple email accounts to Claude · Best AI assistants for multiple email accounts
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."
