Google Workspace MCP Server
One MCP server for Gmail, Calendar, Drive, Docs, Sheets, Slides, Forms, Tasks, Contacts, Chat and Apps Script with OAuth 2.1
- 3,432 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Sends email and edits documents and calendars on the user's behalf
- Stores OAuth tokens with broad account access
Install
- Works in
Manual install
export GOOGLE_OAUTH_CLIENT_ID="..."
export GOOGLE_OAUTH_CLIENT_SECRET="..."
uvx workspace-mcp --tool-tier coreTiers: core, extended, complete. Specific services: --tools gmail drive calendar.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Sends email and edits documents and calendars on the user's behalf
- Stores OAuth tokens with broad account access
This is third-party code. Review the repository files before installing.
What it does
The server connects the agent to twelve Google Workspace services. The agent searches and sends mail, handles drafts and labels, manages calendar events and Drive files, edits Docs, Sheets and Slides, builds forms and reads responses, manages tasks and contacts, and writes and runs Apps Script. Tools are grouped into core, extended and complete tiers; you can pick individual services and enable read-only mode. It runs over stdio or Streamable HTTP with multi-user auth, and a CLI calls tools from scripts.
Who it is for. For Google Workspace users who want to hand mail, calendar and documents to an agent.
Good fit when
- You need to triage unread mail and draft replies
- You need to find free time and schedule a meeting
- You need to move data from a sheet into a doc or deck
Not a fit when
- Your mail and docs live in Yandex 360 or another service
- You cannot create an OAuth client in Google Cloud
Example request
Find unread client emails from this week and schedule a meeting with each next weekMCP
- Transport
- stdio, http
- Authentication
- OAuth
Environment variables
GOOGLE_OAUTH_CLIENT_IDrequired- Google Cloud OAuth client ID
GOOGLE_OAUTH_CLIENT_SECRETrequired, secret- OAuth client secret
MCP_ENABLE_OAUTH21- Enables OAuth 2.1 mode for HTTP
WORKSPACE_MCP_PORT- HTTP server port
GOOGLE_OAUTH_REDIRECT_URI- OAuth redirect URI
Limitations
Requires your own OAuth client in Google Cloud Console with the APIs enabled. Google Chat needs a Workspace account and extra setup. Access to Google Cloud and some APIs from Russia is unreliable. For Claude Desktop the recommended path is HTTP mode added as a Connector.
How to disable. Run claude mcp remove workspace-mcp, stop the server and revoke the app's access in your Google account security settings.
FAQ
Does the server send data anywhere besides Google?
The author says no: there is no telemetry, and OpenTelemetry tracing stays off unless you configure it.
How do I cut down the tool count?
Use --tool-tier core, pick services with --tools or drop tools with --disabled-tools.
Discussion
No questions or reviews yet.
Related
MCP serversGoogle Docs MCP: Docs, Sheets, Drive, Gmail and Calendar
Google Docs MCP
An MCP server giving an agent Google Docs, Sheets, Drive, Gmail, Calendar and Apps Script: reading, editing, mail and events; sign-in over OAuth
GSuite MCP
mcp-gsuite
A Python MCP server for Gmail and Google Calendar: search and read emails, drafts and replies, events with attendees, several accounts at once
A Gemini CLI extension for working with Google Docs, Sheets, Slides, Gmail, Chat, Calendar and Drive from the terminal
A CLI for every Google Workspace API with JSON output and agent skills: Drive, Gmail, Calendar, Sheets and more
An MCP server that gives the agent access to mail, calendar, OneDrive files and Power Automate flows through Microsoft Graph
Yandex Calendar MCP with a setup CLI
yandex-mcp workspace
A Yandex Calendar MCP server over CalDAV with a separate CLI for setup and app-password verification
README in short
The README covers the service scope, tool tiers and two auth modes: confidential client and OAuth 2.1 with PKCE. It gives uvx launch commands and connection steps for Claude Code, Claude Desktop and ChatGPT. Security sections state that data goes only to Google APIs. Detailed deployment, proxy and environment variable docs live on the website. MIT licensed.