Multi Account MCP For Gmail, Calendar, Drive, Docs, And Sheets — 61 Tools, Token
Let your coding agent read and act on Gmail, Calendar, Drive, Docs, and Sheets across multiple Google accounts without leaving the IDE.
Overview
google-workspace-mcp is a MCP server for the Build phase that exposes 61 token-oriented tools for multi-account Gmail, Calendar, Drive, Docs, and Sheets over stdio.
What is this MCP server?
- 61 MCP tools across Gmail, Calendar, Drive, Docs, and Sheets in one server
- Multi-account support so personal and business Google identities stay separate
- Token-efficient tool design aimed at lower context burn per action
- stdio transport with MCPB package and pinned fileSha256 for reproducible installs
- Documented for macOS-oriented solo builder workflows
- Server version 0.1.0 with stdio MCPB registry package
- Requires GOOGLE_OAUTH_CLIENT_ID and GOOGLE_OAUTH_CLIENT_SECRET environment variables
Community signal: 1 GitHub stars.
What problem does it solve?
Your agent cannot see the emails, files, and calendars where real customer and launch work lives unless you paste exports or maintain fragile custom Google API scripts.
Who is it for?
Indie builders on macOS who already live in Google Workspace and want one MCP registration instead of five separate Google integrations.
Skip if: Teams that ban third-party OAuth clients, builders on Google Workspace-free personal Gmail-only setups without Cloud Console access, or anyone who needs Microsoft 365 parity.
What do I get? / Deliverables
After OAuth setup, your agent can query and mutate Workspace resources through MCP tools so specs, threads, and spreadsheets stay in sync with what you ship.
- Registered MCP server your agent can call for Gmail, Calendar, Drive, Docs, and Sheets
- Multi-account Workspace access through 61 structured tools instead of ad hoc API scripts
Recommended MCP Servers
Journey fit
Google Workspace sits in the build phase as live product and ops glue—agents need OAuth-backed APIs to sync specs, invoices, and customer threads while you ship. Integrations is the canonical shelf for third-party MCP bridges that replace bespoke OAuth scripts with stdio tool calls.
How it compares
Workspace-wide MCP bridge with 61 tools, not a single-purpose Gmail-only skill or a hosted Zapier-style connector.
Common Questions / FAQ
Who is google-workspace-mcp for?
Solo and indie developers who use Claude Code or Cursor on macOS and want agents to work inside Gmail, Calendar, Drive, Docs, and Sheets across more than one Google account.
When should I use google-workspace-mcp?
Use it during build and operate work when you need the agent to file support replies, update launch spreadsheets, attach Drive docs to tickets, or schedule follow-ups without manual copy-paste.
How do I add google-workspace-mcp to my agent?
Create OAuth client ID and secret in Google Cloud Console, set GOOGLE_OAUTH_CLIENT_ID and GOOGLE_OAUTH_CLIENT_SECRET, install the v0.1.0 MCPB stdio package from the GitHub release, and register the server in your agent’s MCP config.