Multi Google MCP
Multi-account Google MCP server for Claude Code β Gmail, Drive, Calendar, Sheets, Docs, Contacts, Search Console. 83 tools with OAuth2 multi-account switching.
Documentation
mcp-google-multi
The most complete local Google Workspace MCP server: Gmail, Drive, Calendar, Sheets, Docs, Slides, Forms, Contacts, Tasks, Chat, Meet, Analytics (GA4), Search Console, Classroom, Vault, Admin and more β every OAuth-reachable API method as a tool, across multiple Google accounts at once, from Claude Code or any MCP client.
- π§° Exhaustive β 942 tools across 29 services, now including Google Analytics (GA4), + an escape hatch for anything else β COVERAGE.md
- π Multi-account β drive any number of Google accounts by alias, or fan one call out across all of them
- π Private by design β your own OAuth app, tokens encrypted at rest (AES-256-GCM), writes deny-by-default, no telemetry, no metering β it talks only to Google
- π Local or remote β runs locally over stdio, or self-hosted over HTTP with its own built-in OAuth 2.1 server (Claude Code's
/mcplogin and the claude.ai connector, zero custom UI). Pull-and-up Docker Compose with optional automatic HTTPS β remote setup - βοΈ Built for real work β send and read email in Markdown with attachments and one-call replies, an interactive setup wizard with a
doctorself-check, and per-account scope profiles β features tour
Quick setup
New to all this? It's written for someone who just installed Claude Code and has never made an API key. Copy-paste each step; it says what you'll see. (Already technical? The Configuration reference is the terse version.)
-
Install it. Get Node.js (the green "LTS" button, version 22 or newer), then run:
npm install -g mcp-google-multiClaude Desktop user? You can skip npm entirely: download the
mcp-google-multi.mcpbbundle from the latest release, double-click it (or drag it into Claude Desktop β Settings β Extensions), and fill in the values from step 2 when prompted. -
Make your Google key (the one manual part, a few minutes, because Google has no way to script it). Follow the step-by-step Google Cloud setup, or just ask Claude Code: "walk me through creating a Google OAuth Desktop client for mcp-google-multi." You finish with two values, a Client ID and a Client Secret. It's free and private to you.
-
Put them in a file. In the folder you'll run from, make a file named
.envand paste this, filling in your values:GOOGLE_CLIENT_ID=paste-your-client-id GOOGLE_CLIENT_SECRET=paste-your-client-secret # any short nickname, then your Gmail address: GOOGLE_ACCOUNTS=me:you@gmail.comNo encryption key to make: the server generates and stores one for you.
-
Sign in. A browser opens; pick your account and click Allow:
mcp-google-multi auth --account me -
Add it to Claude Code, then restart Claude Code:
claude mcp add mcp-google-multi -s user -- npx -y mcp-google-multi
Stuck at any point? Run mcp-google-multi doctor. It inspects every part and prints the exact fix for anything wrong (a missing sign-in, a Google API you still need to switch on, and so on). Once it reads all-green, just talk to Claude: "summarize my unread email."
Got more than one Google account? Add them together, like GOOGLE_ACCOUNTS=me:you@gmail.com,work:you@company.com, and run step 4 once per nickname.
On a server or from claude.ai? Advanced path: Remote / HTTP setup. Coming from v5? v6 migration guide.
Go deeper: Configuration reference Β· What's covered Β· Features tour Β· Remote / HTTP setup Β· Secrets in a vault Β· Local usage metrics Β· Migrating to v6 Β· Security policy Β· Roadmap
Agent skill
The repo and the npm package both ship an Agent Skill at skills/google-workspace/: a hand-written SKILL.md covering account selection, the discover step, incremental Gmail sweeps, keeping results small, write profiles, and the escape hatch, plus a reference/ folder with a generated argument table per service. Loading it gets an agent calling this server's tools correctly without guessing argument names.
To install it for Claude Code, copy or symlink the skills/google-workspace folder into ~/.claude/skills/ (every project) or a project's own .claude/skills/ (that project only):
# from a cloned copy of this repo
ln -s "$(pwd)/skills/google-workspace" ~/.claude/skills/google-workspace
# from the installed npm package
ln -s "$(npm root -g)/mcp-google-multi/skills/google-workspace" ~/.claude/skills/google-workspace
Maintainer, sponsor & license
Built and maintained by Abdelbaki Berkati β berkati.xyz Β· @bakissation. Read the case study β
Development is funded by IdeaCrafters (@IdeaCraftersHQ) β the studio that pays for this OSS to exist.
An Enterprise Edition (hosted, multi-tenant) is available: ask through berkati.xyz (email or LinkedIn there).
Thanks to contributors @obatried, @trevor-commits, and @mjreddy. The project is maintainer-led (roadmap on Milestones; bug reports welcome, feature PRs by prior agreement β see CONTRIBUTING.md). Feedback shapes the roadmap: open an issue with bugs, pain points, or what you wish it did. Security reports go to SECURITY.md, never a public issue.
Licensed under MIT.