Google Workspace
Give your coding agent Gmail, Calendar, Drive, and related Google Workspace actions via one manifest-driven MCP server.
Overview
Google Workspace MCP is a Build-phase MCP server that gives agents manifest-driven, multi-account access to Gmail, Calendar, Drive, and related Workspace apps.
What is this MCP server?
- Gmail, Calendar, Drive, and additional Workspace surfaces in one MCP server
- Multi-account support with manifest-driven tool configuration
- stdio @aaronsb/google-workspace-mcp version 2.7.1
- Google OAuth 2.0 Desktop client via GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET
- Suited to solo builders juggling founder email, calendar, and file storage
- Registry version 2.7.1
- OAuth env vars: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET
- stdio npm package @aaronsb/google-workspace-mcp
What problem does it solve?
Solo builders repeat OAuth boilerplate and tab-hop across Google apps when agents cannot natively read mail, events, or Drive files.
Who is it for?
Founders who run their business on Google Workspace and want one MCP integration for mail, calendar, and files while building automations.
Skip if: Teams standardized on Microsoft 365 only, or builds that need granular Admin SDK-only controls without Workspace end-user APIs.
What do I get? / Deliverables
After OAuth setup, one MCP registration lets agents orchestrate Workspace tasks from your coding environment across accounts you define in the manifest.
- Unified MCP access to configured Workspace apps
- Multi-account manifests for separated personal and business Google logins
- Agent-driven email, calendar, and Drive operations from the IDE
Recommended MCP Servers
Journey fit
How it compares
Google Workspace MCP bridge, not a single-purpose Gmail-only skill.
Common Questions / FAQ
Who is Google Workspace MCP for?
Solo and indie builders using Google Workspace daily who want agents to act on Gmail, Calendar, and Drive from MCP clients.
When should I use Google Workspace MCP?
Use it when you integrate founder operations—email, scheduling, files—into agent workflows during build or customer lifecycle work.
How do I add Google Workspace MCP to my agent?
Create Google OAuth Desktop credentials, set GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET, install @aaronsb/google-workspace-mcp stdio, and follow the server manifest for accounts and scopes.