English Français العربية

Google Workspace (multi-account)

Official registry Productivity

Multi-account Google Workspace MCP server: 942 tools, 29 services, discover-first, BYO OAuth.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package mcp-google-multi
Claude Code 
claude mcp add google-workspace-multi-account -e 'GOOGLE_CLIENT_ID=<GOOGLE_CLIENT_ID>' -e 'GOOGLE_CLIENT_SECRET=<your google_client_secret>' -e 'GOOGLE_ACCOUNTS=<GOOGLE_ACCOUNTS>' -e 'MASTER_KEY=<your master_key>' -- npx -y mcp-google-multi@6.1.1
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "google-workspace-multi-account": {
            "command": "npx",
            "args": [
                "-y",
                "mcp-google-multi@6.1.1"
            ],
            "env": {
                "GOOGLE_CLIENT_ID": "<GOOGLE_CLIENT_ID>",
                "GOOGLE_CLIENT_SECRET": "<your google_client_secret>",
                "GOOGLE_ACCOUNTS": "<GOOGLE_ACCOUNTS>",
                "MASTER_KEY": "<your master_key>"
            }
        }
    }
}

Environment variables

  • GOOGLE_CLIENT_ID required OAuth 2.0 Desktop client ID from your own Google Cloud project (docs/google-cloud-setup.md).
  • GOOGLE_CLIENT_SECRET required secret OAuth 2.0 Desktop client secret paired with GOOGLE_CLIENT_ID.
  • GOOGLE_ACCOUNTS required Comma-separated alias:email pairs, e.g. work:you@company.com,personal:you@gmail.com.
  • MASTER_KEY secret Base64 32-byte key encrypting the local token store; auto-generated and stored for you when unset.
OCI package ghcr.io/bakissation/mcp-google-multi:6.1.1
Claude Code 
claude mcp add google-workspace-multi-account -e 'GOOGLE_CLIENT_ID=<GOOGLE_CLIENT_ID>' -e 'GOOGLE_CLIENT_SECRET=<your google_client_secret>' -e 'GOOGLE_ACCOUNTS=<GOOGLE_ACCOUNTS>' -e 'MASTER_KEY=<your master_key>' -- docker run -i --rm ghcr.io/bakissation/mcp-google-multi:6.1.1
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "google-workspace-multi-account": {
            "command": "docker",
            "args": [
                "run",
                "-i",
                "--rm",
                "ghcr.io/bakissation/mcp-google-multi:6.1.1"
            ],
            "env": {
                "GOOGLE_CLIENT_ID": "<GOOGLE_CLIENT_ID>",
                "GOOGLE_CLIENT_SECRET": "<your google_client_secret>",
                "GOOGLE_ACCOUNTS": "<GOOGLE_ACCOUNTS>",
                "MASTER_KEY": "<your master_key>"
            }
        }
    }
}

Environment variables

  • GOOGLE_CLIENT_ID required OAuth 2.0 Desktop client ID from your own Google Cloud project.
  • GOOGLE_CLIENT_SECRET required secret OAuth 2.0 Desktop client secret paired with GOOGLE_CLIENT_ID.
  • GOOGLE_ACCOUNTS required Comma-separated alias:email pairs, e.g. work:you@company.com,personal:you@gmail.com.
  • MASTER_KEY required secret Base64 32-byte key encrypting the local token store.
MCPB package https://github.com/bakissation/mcp-google-multi/releases/download/v6.1.1/mcp-google-multi.mcpb

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. mcp-google-multi
  2. Quick setup
  3. Agent skill
  4. Maintainer, sponsor & license

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 /mcp login 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 doctor self-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.)

  1. Install it. Get Node.js (the green "LTS" button, version 22 or newer), then run:

     npm install -g mcp-google-multi

    Claude Desktop user? You can skip npm entirely: download the mcp-google-multi.mcpb bundle 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.

  2. 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.

  3. Put them in a file. In the folder you'll run from, make a file named .env and 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.com

    No encryption key to make: the server generates and stores one for you.

  4. Sign in. A browser opens; pick your account and click Allow:
     mcp-google-multi auth --account me
  5. 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.

Frequently asked questions

What is Google Workspace (multi-account)?

Multi-account Google Workspace MCP server: 942 tools, 29 services, discover-first, BYO OAuth.

How do I install Google Workspace (multi-account)?

It runs on your machine. In Claude Code: claude mcp add google-workspace-multi-account -e 'GOOGLE_CLIENT_ID=<GOOGLE_CLIENT_ID>' -e 'GOOGLE_CLIENT_SECRET=<your google_client_secret>' -e 'GOOGLE_ACCOUNTS=<GOOGLE_ACCOUNTS>' -e 'MASTER_KEY=<your master_key>' -- npx -y mcp-google-multi@6.1.1. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Google Workspace (multi-account) need an API key?

Yes. It expects GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, GOOGLE_ACCOUNTS, MASTER_KEY, which you set in its configuration.

Is Google Workspace (multi-account) open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Google Workspace (multi-account)?

It is published by bakissation. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.