The server exposes one discover tool per service instead of listing everything, so idle context stays small and calling drive_discover is what reveals Drive's operations. Multi-account is the other half: one read call can fan out across your work and personal accounts and come back with a result per account, and one account failing does not hide the others.
A local Google Workspace MCP server covering every OAuth-reachable Workspace API method, across multiple Google accounts, through your own OAuth app.
- 872 tools across 28 services — Gmail, Drive, Calendar, Sheets, Docs, Slides, Forms, Contacts, Tasks, Chat, Meet, Classroom, Vault and Admin
- Multiple Google accounts by alias; read tools accept an account list, or all of them at once, returning per-account results
- Discover-first listing: a service's operations appear only after you call its discover tool, such as drive_discover
- An escape hatch for anything not covered by a named tool — google_api_search and google_api_call
- Copying or moving a file between two of your own accounts — drive_transfer
- Capped, compact responses: drive_read pages at 100k characters, gmail_read caps message bodies at 50k
- Writes deny-by-default, tokens encrypted at rest with AES-256-GCM, no telemetry and no metering
Node.js 20 or newer, then npm install -g mcp-google-multi. You create your own free Google Cloud app for GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET, name each account in GOOGLE_ACCOUNTS, and supply a MASTER_KEY that encrypts stored tokens. Sign each account in with mcp-google-multi auth --account work.
One command plus a key — npm install -g mcp-google-multi, then supply credentials