mcp-google-multi
mcp-google-multi is a local/remote Google Workspace MCP server that exposes nearly every OAuth-reachable Google API method as a tool across multiple Google accounts.
Access Gmail, Drive, Calendar, Sheets, Docs, Slides, Forms, Contacts, Tasks, Chat, Meet, Analytics, Search Console, Classroom, Vault, Admin, and more via 944 tools across 29 services.
Use multiple Google accounts by alias, or fan one call out across accounts.
Discover curated tools per service or all at once, and use
google_api_search/google_api_callas an escape hatch for any Workspace REST method.Perform reads and writes such as sending/reading email, managing files, calendar events, spreadsheets, docs, contacts, and tasks, with deny-by-default writes and confirmation for write calls.
Manage accounts: add accounts, re-authenticate, list accounts, inspect token/scope status, and run health diagnostics.
Run locally over stdio or self-hosted over HTTP with OAuth login and optional Docker Compose/HTTPS.
Keep data private with your own OAuth app, encrypted tokens, no telemetry or metering, and optional local usage metrics.
Install via npm or Claude Desktop bundle, use the setup wizard/doctor, and optionally load the bundled Agent Skill for correct tool usage.
Allows reading and managing Gmail messages, including sending emails, searching, and managing labels across multiple Google accounts.
Provides integration with Google Workspace services (Gmail, Drive, Calendar, Sheets, Docs, Contacts, Tasks, Meet, Search Console, plus optional Forms, Chat, Workspace Admin) across multiple Google accounts, with read-only by default and configurable write permissions.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-google-multi show my upcoming events from my work calendar"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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 โ 944 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 meAdd 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
Related MCP server: google-workspace-mcp
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-workspaceMaintainer, 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.
Available Tools
19 toolsaccount_addADestructiveIdempotent
Add a new Google account: pass alias + email directly (plus optional bundles/allBundles/admin), or pass nothing for an interactive form where the client supports elicitation. Writes the registry and runs Google consent in the browser. No file editing or restart needed to use the account (tools of a service it newly enables register at the next restart). Requires GOOGLE_CLIENT_ID/SECRET (run the setup prompt first if missing).
Inputs: admin, alias, email, account, +2 more.
account_listARead-onlyIdempotent
List the configured Google accounts: alias, email, admin flag, token status (ok / expired_refreshable / needs_reauth / missing / decrypt_error), and which one is the default. Pass verbose: true for the full per-account report (granted vs configured scopes).
Inputs: verbose.
account_reauthADestructiveIdempotent
Re-authenticate an existing Google account (recover a dead refresh token, or grant scopes after a profile change). Runs Google consent in the browser. Pass the account alias.
Inputs: alias, account.
account_write_configADestructiveIdempotent
Register this server with your MCP client (Claude Code / Claude Desktop / Cursor) so you don't hand-edit JSON. Default: returns the exact snippet/command to add. Pass write:true to write detected file-based configs in place (backs up first, never clobbers a malformed file). Secrets are never inlined.
Inputs: name, write, client.
calendar_discoverBRead-onlyIdempotent
Discover calendar: lists the catalog and reveals its hidden tools; call first, then call the tool by name. Ops: list_calendars, list_events, get_event, create_event, update_event, respond_event, delete_event, quick_add, move_event, list_instances +6 more; 24 generated ops: acl, calendars, calendar, events, settings, channels +1 areas.
Inputs: query.
contacts_discoverARead-onlyIdempotent
Discover contacts: lists the catalog and reveals its hidden tools; call first, then call the tool by name. Ops: search, search_directory, resolve, get, list, create, update, delete, groups_list, group_members +1 more; 13 generated ops: people, contact, other.
Inputs: query.
diagnoseARead-onlyIdempotent
Health report for this server: runtime, config, keys, per-account token status, scope grants, and API enablement. Read-only; returns copy-pasteable fixes for anything wrong. Call this to diagnose auth/config failures.
Inputs: no named parameters.
discover_allARead-onlyIdempotent
Reveal ALL curated Google tools at once (instead of per-service discovery). Use when starting substantial Google work; prefer these over google_api_call. Pair with discover_reset.
Inputs: no named parameters.
discover_resetARead-onlyIdempotent
Collapse the tool surface back to the configured default, reclaiming context budget after heavy Google work. All tools remain callable by name after collapsing.
Inputs: no named parameters.
docs_discoverARead-onlyIdempotent
Discover docs: lists the catalog and reveals its hidden tools; call first, then call the tool by name. Ops: create, get, read, insert_text, replace_text, delete_range, update_style, insert_table, create_named_range, delete_named_range +17 more.
Inputs: query.
drive_discoverARead-onlyIdempotent
Discover drive: lists the catalog and reveals its hidden tools; call first, then call the tool by name. Ops: search, read, list, upload, download, export, create_folder, update, delete, trash +26 more; 35 generated ops: approvals, files, drives, teamdrives, changes, apps +6 areas.
Inputs: query.
gmail_discoverARead-onlyIdempotent
Discover gmail: lists the catalog and reveals its hidden tools; call first, then call the tool by name. Ops: search, read, read_thread, read_batch, send, download_attachment, create_draft, modify_labels, trash, delete +13 more; 57 generated ops: users.
Inputs: query.
google_api_callADestructive
Invoke any Google Workspace REST method by Discovery id (escape hatch for operations without a dedicated tool). Find methods with google_api_search first. A write asks the connected human to confirm the real call (account, verb, params, a destinations-first body summary) unless GOOGLE_PROFILE=full-writes with no outbound allowlist; GOOGLE_READ_ONLY or a matching GOOGLE_WRITE_DENY still refuse outright. On reads, pass a fields query param (Google partial response) to keep the payload small. Returns JSON only; for binary/file content (media downloads, drive.files.export) use drive_download / drive_export instead.
Inputs: api (required), methodId (required), body, account, +2 more.
google_api_searchARead-onlyIdempotent
Search the Google API Discovery index for any Workspace REST method, including ones with no dedicated tool here. Returns method ids + parameters to invoke via google_api_call. APIs: gmail, drive, calendar, sheets, docs, slides, forms, people, searchconsole, tasks, chat, meet, driveactivity, drivelabels, admin_directory, admin_reports, admin_datatransfer, groupssettings, analyticsadmin, analyticsadmin_v1alpha, analyticsdata, appsmarket, classroom, cloudidentity, cloudsearch, groupsmigration, keep, licensing, postmaster, reseller, script, vault, workspaceevents.
Inputs: query (required), api, maxResults.
meet_discoverARead-onlyIdempotent
Discover meet: lists the catalog and reveals its hidden tools; call first, then call the tool by name. Ops: conference_records_list, conference_record_get, recordings_list, transcripts_list, transcript_entries_list; 13 generated ops: conference, spaces.
Inputs: query.
searchconsole_discoverARead-onlyIdempotent
Discover searchconsole: lists the catalog and reveals its hidden tools; call first, then call the tool by name. Ops: sites_list, sites_get, sites_add, sites_delete, sitemaps_list, sitemaps_get, sitemaps_submit, sitemaps_delete, searchanalytics_query, url_inspect; 1 generated ops: url.
Inputs: query.
sheets_discoverARead-onlyIdempotent
Discover sheets: lists the catalog and reveals its hidden tools; call first, then call the tool by name. Ops: create, get, read_range, write_range, append_rows, clear_range, batch_read, batch_write, add_sheet, delete_sheet +20 more; 7 generated ops: spreadsheets.
Inputs: query.
tasks_discoverARead-onlyIdempotent
Discover tasks: lists the catalog and reveals its hidden tools; call first, then call the tool by name. Ops: lists_list, list_get, list_insert, list_update, list_delete, list, get, insert, update, delete +2 more; 2 generated ops: tasklists, tasks.
Inputs: query.
workspaceevents_discoverARead-onlyIdempotent
Discover workspaceevents: lists the catalog and reveals its hidden tools; call first, then call the tool by name. Ops: 15 generated ops: tasks, subscriptions, message, operations.
Inputs: query.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogโฆ
TDQS
Scored across 19 tools
Each per-service discover tool targets a clearly named Google product (gmail, drive, sheets, docs, calendar, contacts, tasks, meet, searchconsole, workspaceevents), so an agent can pick the right one. The main overlaps are discover_all vs. the per-service discovers, and account_list vs. diagnose (both report token status), but descriptions frame these as bulk vs. targeted and registry vs. health, which resolves most confusion. google_api_search/google_api_call are explicitly positioned as an escape hatch, not a duplicate path.
Strong recurring patterns: *_discover for services, account_* for account management, google_api_* for the generic path, discover_all/discover_reset as a pair. Only 'diagnose' breaks the verb_noun convention, and the two discover_* names invert the pattern used by the service discovers, but both are still readable and predictable.
19 top-level tools is slightly above the comfortable band, but the discovery/collapse mechanism (discover_reset, discover_all) is purpose-built to keep context lean while exposing a very large hidden surface. Every visible tool earns a role: service gateways, escape hatch, account lifecycle, diagnostics.
Covers Gmail, Drive, Sheets, Docs, Calendar, Contacts, Tasks, Meet, Search Console and Workspace Events with read/write/delete operations, plus account add/reauth/config/diagnostics and a Discovery-based google_api_call escape hatch for any remaining REST method. No obvious dead ends for the stated Google Workspace purpose.
Maintenance
Related MCP Connectors
Hosted MCP for Google Workspace, Atlassian and Notion: one OAuth, per-user accounts, write access.
Permissioned access to Gmail, Drive and Calendar via the user's own Google account
Gmail, Outlook, Drive, OneDrive and calendars for AI agents. Many accounts, one endpoint, audit log.
Your Gmail, Calendar, Drive, GitHub, Oura, wallet and confirmed profile facts in any MCP client.
Related MCP Servers
- AlicenseAqualityDmaintenanceMCP server for Google Workspace APIs - Docs, Sheets, Drive, Gmail, and Calendar. Enables reading, creating, and editing Google Docs and Sheets, managing comments, reading emails, and viewing calendar events.3453 npm17MIT
- AlicenseCqualityAmaintenanceA multi-account Google Workspace MCP server that drives Gmail, Google Calendar, and Google Drive across any number of Google accounts in parallel from one server.422MIT
- FlicenseBqualityDmaintenanceMCP server providing full access to Google Workspace services (Gmail, Drive, Calendar, Docs, Sheets, Slides, Forms, Tasks, Contacts) using OAuth authentication.1001-
- AlicenseAqualityBmaintenanceEnables natural language interaction with multiple Google accounts (Gmail, Drive, Calendar) from MCP-compatible clients like Claude.6335 npm2MIT