How to Connect Multiple Google Drive Accounts to Grok Bot
Grok Bot has no Google Drive connector. SpaceXAI does not publish one, and the phrase “Google Drive” does not appear anywhere in the Grok Bot documentation. Drive still works, through three hops and three vendors: Grok Bot uses Cursor’s plugin surface, Cursor’s marketplace carries a google-drive plugin, and that plugin is a thin wrapper on Google’s own remote MCP server. Carly holds your OneDrive accounts, and every mailbox and calendar on both sides, in the same place.
Nobody in that chain has written down what happens when you put two Drives behind it.
This is not the Grok that has a Drive connector
The assistant at grok.com genuinely does have a built-in Google Drive connector, with its own New Connector flow and admin provisioning through the cloud console on Business plans. If you read a guide that describes clicking Google Drive in a connector list, that guide is about grok.com. SpaceXAI’s own FAQ draws the line: Grok Bot “is not the same as Grok on grok.com or the Grok mobile apps.”
The plumbing shares nothing. grok.com uses xAI OAuth and the xAI console; Grok Bot uses Cursor authentication, the Cursor marketplace, and a Google server. Our Grok connectors overview covers that side, what Grok Bot actually does covers this one.
Three hops, and none of them is an xAI connector
Hop one: the plugin surface belongs to Cursor. SpaceXAI states it plainly. Grok Bot “follows your team’s existing Cursor plugin and MCP policy,” there are “no separate Grok Bot plugin controls,” and “MCP authentication is shared across Cursor + Grok Bot.” There is no Grok Bot connector catalogue to browse, because the catalogue is Cursor’s.
Hop two: Cursor’s Plugin Marketplace carries a first-party google-drive plugin. Published by Cursor itself, verified, featured and approved, declaring a minimum client version of 3.13.0.
Hop three: the plugin is a wrapper on Google’s remote MCP server. In the open plugin repository, the Google Drive entry is a few lines of configuration pointing at a Google-hosted MCP endpoint. Cursor is not implementing Drive access, it is forwarding you to Google’s server.
Grok Bot itself is gated: SpaceXAI says “eligible plans include SuperGrok Heavy, Cursor Ultra, and Cursor Teams Premium.” Public plan cards stop below Heavy and billing is a weekly usage allowance plus on-demand cost, so treat any figure you see quoted as unconfirmed.
The marketplace blurb overstates what Google exposes
Cursor’s listing says the plugin lets you “search, read, create, share, and manage files.” Google’s own tool reference for its Drive MCP server names eight tools, and share is not among them.
| Verb | Named as a tool? | What exists |
|---|---|---|
| Search | Yes | search_files |
| Read file content | Yes | read_file_content, download_file_content |
| Read metadata | Yes | get_file_metadata, list_recent_files |
| Create a file | Yes | create_file |
| Copy a file | Yes | copy_file |
| Update or edit an existing file | No tool named | absent from the eight |
| Delete or trash | No tool named | absent from the eight |
| Share, or set permissions | No tool named | get_file_permissions only, which reads them |
Trust the tool table over the listing copy. A permissions reader is not a sharing tool, and nothing here edits a document you already have or removes one you no longer want. The scopes requested are drive.readonly and drive.file, and the second is per-file consent rather than whole-Drive write. A granted scope is not an exposed action, so it does not rescue the missing verbs either.
Google’s server is in Developer Preview, and the two setup docs disagree
Google labels the Drive MCP server as available through its Workspace Developer Preview Program, and its setup instructions ask for real work: your own Google Cloud project, two APIs enabled with gcloud, an OAuth consent screen, and your own client ID and secret. Cursor’s plugin README describes something much simpler, where authentication is OAuth 2.0 against Google and Cursor prompts for sign-in when the plugin connects.
Those two documents cannot both be a complete description of the same setup, and whether Cursor is a pre-approved preview client is stated nowhere. If the plugin refuses to authorize, preview eligibility is the first thing to suspect and the 3.13.0 client floor is the second, since how that version maps to a Grok Bot build is undocumented.
A second Drive account has no documented slot
Undocumented and refused are different claims, and this is the former. Nothing in SpaceXAI’s Grok Bot pages addresses holding two accounts of one service, and nothing in the Cursor plugin material does either. There is no statement that a second install replaces the first, and none that it works.
Two lines lean singular without settling it. The troubleshooting guidance says to “complete authorization with the intended account in the browser,” and the remedy for a revoked authorization is to remove and reconnect the plugin. A remove-and-reconnect fix implies one stored authorization per install, which is an inference from the shape of the advice rather than something anyone wrote down.
One workaround that sounds obvious does not exist. You cannot give each Bot its own Drive. SpaceXAI is explicit: “Installed connectors are account-wide. Their availability is not isolated to one Bot.”
A second named MCP server entry pointing at the same Google endpoint, with its own OAuth client, is the structural shape a two-account setup would take, but whether the app lets you add it and whether two authorizations coexist rather than overwrite is untested. On a team plan it may not be your call: Team Settings carries an MCP Configuration section with a global off switch, a server allowlist and denylist, a setting for whether members can add their own servers, and a network allowlist requirement.
The browser reaches several Drives and cannot keep them apart
There is a second path that needs no plugin, and it is a genuine strength. Each Bot drives a real browser on a shared cloud computer, and SpaceXAI says Grok Bot “can use many browser-based tools, including services without a dedicated connector.” Sign a Google account into that browser through computer takeover and drive.google.com is reachable.
Then the catch, which inverts the usual multi-account problem. Browser cookies and signed-in sessions are shared, signing in for one Bot makes the session available to your other Bots, and the per-Bot screens are “separate work surfaces, not separate security boundaries.”
So Google multi-login puts several Drives in one place, and the difficulty is not reach but separation. Every Bot can open every Drive you have signed in, and there is no per-account routing to hand the client Drive to one Bot while withholding your personal one. SpaceXAI’s own suggestion for narrowing this is to “use scoped service accounts where the source system supports them.” Cleanup follows the same rule: deleting a Bot “does not remove shared-computer files or browser sessions,” so the real revocation is signing out and removing the plugin.
Nothing fires when a file lands in Drive
Grok Bot can react to events, not just timers, which puts it ahead of assistants that only schedule. The reach is the catch: event triggers come through Cursor account integrations and the documented examples are a Slack message and a GitHub notification, each needing its own connection flow separate from the matching plugin.
So the documented trigger vocabulary is a clock, a Slack message, and a GitHub notification, with those event integrations separate from the matching plugins and possibly needing their own connection flow. Starting on an event at all is more than most assistants manage and deserves credit.
It does not reach Drive. A file arriving in a folder, a document edited by a colleague, a folder shared with you: none of those appear in any SpaceXAI document, and Google’s server has no subscription primitive to build one from, since all eight of its tools pull rather than push. The nearest approximation is a scheduled routine that lists recent files and compares them against what it saw last time, within the documented caps of 50 routines per Bot and the 20 most recent run records.
1. Sort your case
| What you have | Native path in Grok Bot |
|---|---|
| Searching and reading one Google Drive | Cursor’s google-drive plugin, no xAI connector |
| Editing a document already in Drive | No tool named in Google’s reference |
| Deleting a file, or sharing one | No tool named; permissions can only be read |
| A second Google account | Not documented either way |
| Keeping two Drives apart per Bot | Not available; plugins and sessions are account-wide |
| A file landing in Drive starting a routine | Not documented; every Drive tool pulls |
| No plugin available to you | The shared browser at drive.google.com |
2. Add the Google Drive plugin
- Press
Cmd/Ctrl+,to open settings. - Go to Plugins, then Marketplace.
- Find Google Drive, published by Cursor, and click Add.
- Complete the Google sign-in in the browser that opens.
- Read the address on the consent screen before you approve it.
- Check the plugin under Yours, then type
@in a chat to attach it.
If it never appears, work through the order above: team MCP policy, then the 3.13.0 client floor, then Developer Preview eligibility.
3. Put an approval rule on writing before you add a second Drive
Grok Bot supports Auto-review rules, and a Require Approval rule always stops a matching action. Add one covering file creation before any Bot can reach more than one Drive, so searches run freely while a file headed for the wrong company’s folder stops in front of you. An approval “covers the proposed action only” and does not undo work already done, which is the argument for setting it up first.
4. Bring the second Drive in without a second plugin
- Sign into Google Drive as the second account.
- Select the folders the Bot genuinely needs, not the whole Drive.
- Share them with the Google address you authorized in the plugin.
- Or move the files into a shared drive that both accounts can open.
- Accept anything pending in the connected account.
- Ask the Bot to search for one file you know is in the shared folder.
That last step matters. drive.readonly covers items shared with the connected account, so search_files should see them, but that is an inference from the scope rather than a documented capability, and one known file is the whole verification.
5. Connect each Google account to Carly
- Sign in at carlyassistant.com.
- Open carlyassistant.com/integrations.
- Find Google Drive and click Connect.
- Authorize the first Google account and confirm the address that comes back.
- Click Connect on Google Drive again for the next identity, choosing Use another account.
- Repeat for every remaining account, personal, freelance or Workspace.
No sharing to maintain in Google, no service accounts, and each Drive stays its own addressable identity rather than another session in one browser.
6. Add Carly to Grok Bot
- Select Plugins in the Grok Bot sidebar, or tap your avatar and choose Plugins on mobile.
- Add Carly’s remote MCP server,
https://carlyassistant.com/mcp/. - Finish the authorization in the browser tab that opens. If it sits on Waiting for authorization, use Reopen.
- Sign in to the Carly account holding the connections above.
- Confirm Carly appears under Installed.
Grok Bot takes remote MCP servers rather than local ones, and Carly’s is hosted, so it qualifies. Plugin connections belong to your Grok Bot account rather than an individual Bot, and team plans inherit Cursor’s MCP policy, so an admin can gate it.
7. Test read-only, then name the Drive every time
One account per prompt until routing is reliable:
In my personal Drive, find the three most recently modified files and give me the folder each one sits in. Do not change anything.
Then the question a single plugin install cannot answer:
Search my personal Drive and the Wayfair Drive for anything named like a renewal schedule in the last 60 days, and name the source account on every row.
Then keep the account named on anything that writes:
Create the handover doc in the Wayfair Drive, in the Client Onboarding folder. Do not put it in my personal Drive.
Grok Bot versus Carly on Google Drive
| Need | Grok Bot | Carly |
|---|---|---|
| Search and read Drive files | Yes, via Cursor’s plugin | Yes |
| A first-party connector from the assistant vendor | No, three vendors deep | Yes |
| Reach a service with no connector at all | Yes, the real browser | Yes, with your own API key |
| Edit a document already in Drive | No tool named | Yes, appends to a Google Doc |
| Hold two Google accounts as separate connections | Not documented | Yes |
| Keep two Drives separable once connected | No, sessions and plugins are account-wide | Yes, each identity is addressable |
| Set up without an admin decision on a team plan | Admin can block MCP entirely | Yes, you authorize it yourself |
| Start work when something arrives, not on a clock | Schedule, Slack or GitHub only | Yes, on mail and calendar events |
Grok Bot earns the browser row. A persistent cloud computer running a real browser is a better answer to “there is no connector for this” than any tool list, and it is the reason Drive is reachable here at all. If you live in one Google account and want a Bot that can open anything on the web, the plugin chain is worth the setup.
Carly answers the shape that chain cannot. Google Drive is a native connector authorized per identity, so a personal Gmail account and two Workspace accounts sit side by side as separate connections, and one question can span all three with the source named on every row. Nothing lands in a shared browser profile, so separation is the default rather than something you trade away. Carly also acts on the mail and the calendar event as it arrives rather than waiting for a timer, and for a Drive verb outside the native tool set the API path exists and is worth a conversation.
Free Zapier-style workflows; AI agents from $35/month. Connect it on the integrations page, or start with Google Drive.
Quick fixes
| Problem | Fix |
|---|---|
| No Google Drive connector anywhere in Grok Bot | There is not one; the path is Cursor’s google-drive plugin under Settings then Plugins |
| The guide you read describes a connector list | That guide is about grok.com, which has a genuine built-in Drive connector and different plumbing |
| The plugin is missing from the Marketplace | Check team MCP policy first, then the 3.13.0 client floor; “Disabled by team admin” means an allowlist only an admin can change |
| Authorization fails at the Google screen | Google’s server is in Developer Preview; Cursor’s one-click claim and Google’s own project setup instructions disagree |
| It authorized the wrong Google account | Remove and reconnect the plugin, completing the browser step with the intended account |
| It cannot edit or delete a file | Google’s reference names no update, delete or share tool, only create and copy |
| One Bot per Drive account will not stick | Installed connectors are account-wide, so that boundary does not exist |
Frequently asked questions
Does Grok Bot connect to Google Drive?
Not through an xAI connector. SpaceXAI publishes none, and Grok Bot uses Cursor’s plugin surface instead, where a first-party google-drive plugin forwards to Google’s own remote MCP server. Separately, a Bot can open drive.google.com in the shared browser.
Can I connect two Google Drive accounts to Grok Bot?
Nobody documents it either way. The troubleshooting advice implies one stored authorization per plugin install, but that is an inference rather than a stated limit. The reliable route is sharing the second account’s folders into the account you authorized, or using a shared drive.
Will separate Bots keep my Drives apart?
No. SpaceXAI states that installed connectors are account-wide and not isolated to one Bot, and that the per-Bot screens are separate work surfaces rather than separate security boundaries.
Can Grok Bot edit or delete a file in Drive?
Google’s tool reference for the Drive MCP server names eight tools, covering search, metadata, reading content, creating a file and copying one. There is no update tool, no delete tool and no sharing tool, only a permissions reader. The Cursor listing that promises sharing and managing files goes further than that table supports.
Does anything happen automatically when a file lands in Drive?
Nothing documented. A routine runs on a schedule or on an event from a Cursor account integration, and the documented examples are a Slack message and a GitHub notification. Every Drive tool pulls, so the nearest approximation is a scheduled routine listing recent files.
Related: What Grok Bot does · Multiple Gmail accounts in Grok Bot · Multiple Slack workspaces in Grok Bot · Best AI assistants for Google Drive · MCP servers · Carly’s Google Drive 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."
