What it does
This is an MCP server that exposes Google Workspace services—Gmail, Drive, Calendar, Docs, Sheets, Slides, Chat, Forms, Tasks, Contacts, and Apps Script—to Claude and other MCP clients. It handles authentication via OAuth 2.0/2.1 and provides fine-grained tools for tasks like reading emails, creating documents, managing calendars, editing spreadsheets, and automating cross-service workflows. The server supports both local and remote deployment modes, including stateless container operation and an external OAuth provider pattern for centralized organization-wide hosting.
Who it's for
Software teams and automation engineers who need Claude to manage or interact with Google Workspace data. Common personas include operations teams automating email and document workflows, product managers coordinating schedules across shared calendars, and developers building multi-service automation tools that require read and write access to Gmail, Drive, and workspace documents.
Common use cases
- Automate email triage, labeling, and response drafting within Gmail
- Create, edit, and format Google Docs and Sheets on behalf of users
- Coordinate calendar events and meeting logistics across multiple accounts
- Manage files, permissions, and sharing in Drive
- Chain actions across multiple Workspace apps—for example, fetch data from Sheets, generate a Doc, and email it
Setup pitfalls
- OAuth setup requires a Google Cloud project with appropriate APIs enabled (Gmail, Drive, Calendar, etc.); follow the documented prerequisite steps or authentication will fail
- Multi-user bearer token mode needs careful credential isolation if serving multiple users from one instance
- High risk class due to filesystem writes and network access—audit credential scoping in your Google Cloud IAM role to the minimum required by your use case
- Stateless mode requires external state storage; misconfiguration can lose session or token data across restarts