Google Workspace MCP
A comprehensive MCP server providing AI agent access to the full Google Workspace suite: Gmail, Calendar, Drive, Docs, Sheets, Slides, Forms, Chat, Tasks, Contacts, and Apps Script. Supports OAuth 2.0/2.1, multi-user auth, read-only mode, tool tier filtering, and both HTTP and stdio transports.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Google Workspace MCP (Docs, Sheets, Drive, Gmail). OAuth2 with fine-grained scopes. Handle OAuth tokens carefully — access to email/files is sensitive. Use minimal scopes per use case.
⚡ Reliability
Best When
An agent needs broad, deep integration with Google Workspace services, especially when multiple services (Gmail + Calendar + Drive) are needed together.
Avoid When
You only need one Google service (dedicated single-service MCP servers may be simpler), or you use Microsoft 365 / non-Google productivity tools.
Use Cases
- • AI-assisted email management and Gmail search/compose/reply
- • Natural language calendar management with event creation and scheduling
- • Reading, creating, and editing Google Docs, Sheets, and Slides through agents
- • Managing Google Drive files including search, upload, and Office format conversion
- • Task and contact management through AI agent interfaces
- • Automating Google Apps Script execution via AI agents
Not For
- • Non-Google email or calendar systems (Outlook, iCloud, etc.)
- • Scenarios requiring no Google Cloud setup (OAuth credentials are mandatory)
- • High-security environments where OAuth token storage is a concern
- • Offline or disconnected operation
Interface
Authentication
Requires Google Cloud Project with OAuth 2.0 credentials (client ID + secret). Supports OAuth 2.1 for streamable-http transport. Desktop OAuth clients simplify setup (no redirect URI needed). Multi-user bearer token auth supported. Read-only mode available to restrict scopes. OAUTHLIB_INSECURE_TRANSPORT=1 required for local development.
Pricing
MIT licensed. Google Cloud project required but free tier sufficient for OAuth credentials. Google API quotas apply per service.
Agent Metadata
Known Gotchas
- ⚠ OAuth setup requires creating a Google Cloud project and configuring credentials - significant initial friction
- ⚠ OAUTHLIB_INSECURE_TRANSPORT=1 env var required for local dev is a security concern if forgotten in production
- ⚠ 12 services exposed means potentially overwhelming tool count - use --tool-tier or --tools to filter
- ⚠ Single-user mode cannot be combined with OAuth 2.1
- ⚠ Email send and calendar create are destructive actions - agents should confirm before executing
- ⚠ Google API quotas vary per service and can be hit unexpectedly
- ⚠ Token storage and refresh adds operational complexity for multi-user deployments
Alternatives
Full Evaluation Report
Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Google Workspace MCP.
Scores are editorial opinions as of 2026-03-06.