google_workspace_mcp
Google Workspace MCP Server gives AI assistants natural-language control over Google Calendar, Drive, Gmail, Docs, Sheets, Slides, Forms, Tasks and Chat through any MCP client. The README calls it the most feature-complete Google Workspace MCP server, and says it works with free Google accounts and Workspace plans alike. It supports single-user use and multi-user authentication through OAuth 2.0 and 2.1 with bearer tokens, and setup has been simplified to use Google Desktop OAuth clients, so no redirect URIs or port configuration are needed. A one-click Claude Desktop install is offered.
Features cover end-to-end Gmail management, full calendar management, file operations with Office format support, document creation, editing and comments, and fine-grained control of the other services. You can run it with `uvx workspace-mcp --tool-tier core`, where tool tiers limit which tools are exposed, and some features such as web search need a Google Custom Search setup. It requires Python 3.10+ and your own Google Cloud OAuth credentials. The author discloses that the README was written with AI assistance and verified by a human. The code is MIT licensed.
Features
Why choose it
Trade-offs
Maintenance check
- Last commit
- 2026-10-27
- Commits, last 90 days
- 100+
- Releases, last 90 days
- 23
- Latest release
- v2.2.1 (2026-10-27)
- Open issues
- 93
- Recent issues with at least one comment
- 2/9
Oldest week on the left; the latest four weeks are orange. Source: GitHub commit activity.
Status rule: archived on GitHub = Archived; last commit within 90 days = Active; 91 to 365 days = Slowing; older = Stale. All figures come from the GitHub API on the date shown.
Most discussed open issues
- #193 question: how to pass existing access token without sharing client_secret in single-user setup6 comments · 2025-08-25
- #1077 Opt-in outbound recipient allowlist for unattended/agent deployments5 comments · 2026-08-29
- #912 Feature request: add Gmail draft lifecycle tools5 comments · 2026-07-09
- #861 [feat request] Google Docs: Edit text using Suggestion mode5 comments · 2026-06-18
- #509 Configurable Toolsets via Header / Query Params5 comments · 2026-02-25
Issue titles are quoted from GitHub. Open the link to check whether a problem still applies to the version you use.
Who it fits
- You want one server for Gmail, Drive, Calendar, Docs, Sheets, Slides, Forms, Tasks and Chat instead of one per service.
- Several people will use it: it supports multi-user OAuth 2.0 and 2.1 with bearer tokens.
- You want to limit exposure with tool tiers such as `--tool-tier core`.
- You only need Sheets: a focused server exposes fewer tools and less account access.
- You cannot create your own Google Cloud OAuth credentials: setup requires them.
- Giving an assistant access to Gmail and Drive is not acceptable in your organisation.
How it differs
vs mcp-google-sheets★ 1.0kmcp-google-sheets covers Sheets only, with 19 tools and a Service Account limited to one Drive folder. Google Workspace MCP covers nine services with OAuth.
Compatibility
Quick start
Use cases
Alternatives
Featured in these lists
Comments
No comments yet. Be the first!