Google DriveConnect multiple Google Drive accounts to Claude
Claude's Google Workspace connector authorizes one Google account: Anthropic's help centre says Claude reaches the Gmail, Calendar and Drive data of the single account you connected (Claude Help Center). If your files are split across a work Drive and a personal one — or one Drive per client — the second account means authenticating again, and the first one is gone until you switch back.
This guide uses ProxyLoom to put the Drives of several Google accounts behind a single MCP connection, so Claude can search and read in any of them and you say which one by name. It takes about five minutes and no Google Cloud project or JSON config.
What you end up with
One connector in Claude called ProxyLoom. Behind it, each Google account you connected, with a label you chose (for example work, personal, client-a). Every Drive tool Claude sees carries an account argument, so "find the contract in client-a" and "put the summary in work" both work in the same conversation, without disconnecting anything.
1. Sign up for ProxyLoom
Create an account at https://app.proxyloom.dev/sign-up.
2. Connect each Google account
Signing in puts you on the Connections screen. Click + Connect an account, pick Google Drive, and click Authenticate and connect →. Google's own screen opens; choose the account and allow access. Repeat for each account you want. Each one becomes a separate connection with its own token.
On Google's screen you will currently see "Google hasn't verified this app" after picking the account, but the connection itself is fine. Click Advanced at the bottom left, then Go to ProxyLoom (unsafe), and review the permissions and allow.
Back on the Connections screen, give each connection a label: click Add a label in that connection's Label column. The label is the name you will use when you talk to Claude, so use what you already call that Drive:
work,personal, the client's name. Without a label ProxyLoom falls back to the address Google reports.3. Add ProxyLoom to Claude
In Claude, open Settings → Connectors and click Add (top right). The Add custom connector dialog opens: give it a name — ProxyLoom — paste your ProxyLoom URL as the MCP server URL, and continue. The URL sits in the MCP Endpoint bar at the top of ProxyLoom's Connections screen, with a copy button next to it.
Continuing opens ProxyLoom's authorization in your browser: sign in once and approve, and the connector is authorized. That is the only connection Claude holds.
This works the same in the Claude desktop app, claude.ai and Claude Code. Any client that speaks Streamable HTTP MCP and OAuth 2.1 (Codex, Cursor, ChatGPT) is set up much the same way, with the same URL.
4. Use it
Ask Claude to list the connected accounts to confirm everything is there:
Which Drives do you have?
Claude asks ProxyLoom and answers with the labels. From then on, name the account in the request:
Find the contract in client-a that mentions the renewal date and summarize it.
Write that summary into a new doc in work.
If a request is ambiguous, Claude asks which Drive you mean rather than guessing. Which account was used is recorded in ProxyLoom's audit log, so you can check afterwards.
Notes
- There is nothing to set up on the Google side. Each connection carries only what you allowed on Google's consent screen: reading the Drive, and creating files — it can edit or delete only the files it created itself, never the rest of your Drive. You can revoke the grant at any time: delete the connection on ProxyLoom's Connections screen, or remove ProxyLoom from the third-party connections in your Google account.
- Adding an account later does not mean repeating step 3, Add ProxyLoom to Claude — that one is done once and never again. Connect the account on ProxyLoom's Connections screen, and Claude sees it from then on.