Skip to content

google-multi-account

Multi-account Google Workspace for LLM agents — 100% local.

Connect Claude Desktop, Claude Code or Cursor to several Google accounts through a local MCP server. The agent can request access; only you grant it — every unlock, every Drive zone, every new account stays a human action.

  • Get started Install without cloning, connect an account, ask the LLM.

  • Security first Default-deny, per-profile locks, zoned Drive writes, zero mail sending.

  • CLI (mag) mag: profiles, locks, Drive zones, Touch ID.

  • Under the hood MCP, gateway, loopback broker, wrapper — who talks to whom.

What you get

  • Multi-account, not a single token — each account is a profile with its own policy, locks and Drive zones. The agent targets an alias, never "your Google" as a whole.
  • The human holds every door — unlock, Drive zone, new account, IAM fix: the agent proposes the exact command (elicitation), you run it.
  • Default-deny by design — any undeclared service is refused; the Gmail tools stop at the draft (no sending); Drive writes stay inside the granted folders.
  • 100% local — encrypted tokens (AES-256-GCM, master key in the macOS Keychain), audit log per client. The only cloud step: one OAuth credential, once.

Install

Prerequisites — the upstream gws CLI (the Google Workspace CLI this project wraps) and Python 3:

brew install googleworkspace-cli

Then, to use the server (no need to clone the repository):

curl -fsSL https://raw.githubusercontent.com/elzinko/google-mcp-multi-account/main/install.sh | bash

This downloads the latest version, puts it on your machine, wires up Claude Desktop and Claude Code (Cursor: wire it by hand), and prints at the end the remaining Google setup (one OAuth project, ~10 min — see OAuth / Google Cloud). No account connects until that is done — but setup_status already runs to guide you.

Once the Google setup is done, connect an account, then restart Claude Desktop:

mag add perso votre.email@gmail.com   # "perso" = short name · the email pins the account
mag list             # profiles + state

Update later, still without cloning:

mag update

Cloning is for contributing

The git clone is only needed to develop the project. See Install & update and Contributing.

Going further

I want to… Page
Wire up a client, see the exposed tools Install & update
Do the OAuth / Google Cloud setup, IAM roles OAuth / Google Cloud
Drive mag (profiles, locks, Drive zones) CLI (mag)
Drive the web admin (accounts, locks, policies) Web admin
Understand the policy model (default-deny, zones) Policy model
See the security guarantees, phase by phase Threat model
An honest look (strengths, limits, competition) Critique

Open-source project (MIT), built in spare time. A security concern? SECURITY.md.