Google Workspace MCP Server 
Full natural language control over Google Calendar, Drive, Gmail, Docs, Sheets, Slides, Forms, Tasks, Contacts, and Chat through all MCP clients, AI assistants and developer tools. Includes a full featured CLI & Code Mode for use with tools like Claude Code and Codex!
The most feature-complete Google Workspace MCP server, it can do things that Google's own tooling and the built in integrations with Claude and ChatGPT can't come close to. With multi-user support, rich fine-grained editing tools and the most extensive coverage of any Google Workspace tool in existence, Workspace MCP is in a different class.
By leveraging native OAuth 2.1, stateless deployment capability and external auth server & gateway passthrough auth support, it's also the only Workspace MCP you can host for your whole organization centrally & securely!
Support for all free Google accounts & Google Workspace plans (Starter, Standard, Plus, Enterprise, Non Profit) with expanded app options like Chat & Spaces.
Interested in a private, managed cloud instance? That can be arranged.
See it in action:
What It Does
Workspace MCP connects AI assistants to all twelve major Google Workspace services - 120+ tools behind a single MCP server, with OAuth 2.1 multi-user auth, three progressive tool tiers, read-only mode, a full CLI, and stateless container deployment. It runs locally over stdio for legacy clients and remotely over streamable HTTP with full implementation of the latest MCP spec.
The README covers just enough to get you running, with extensive documentation on the website:
| Where to go | What you'll find |
|---|---|
| Quick Start | Google Cloud setup, credentials, and client connection with screenshots |
| Full Documentation | Every tool, parameter, and auth mode |
| Advanced Deployment | Reverse proxy & nginx config, origin validation, credential store backends (GCS/CMEK), and the complete environment variable reference |
| Client Setup Guides | Claude Desktop/web Connectors, ChatGPT Developer Mode, and more |
| FAQ & Troubleshooting | OAuth errors, redirect URIs, Google Chat setup, client quirks |
Security & Compliance
|
For Security Teams By default, this server sends no data anywhere except Google's APIs, on behalf of the authenticated user, using your own OAuth client credentials. There is no usage reporting, analytics, license server, or SaaS dependency outside optional OTel support for your own usage.
Full dependency tree in |
For Legal & Procurement This project is MIT licensed — not "open core," not "source available," not "free with a CLA." There is no dual licensing, no commercial tier gating features, and no contributor license agreement.
|
Services
📧Gmail15 tools - search, send, draft, labels, filters, attachments |
📁Drive16 tools - search, create, share, import Office files |
📅Calendar7 tools - events, free/busy, Out of Office, Focus Time |
📝Docs19 tools - edit, style, tables, tabs, comments, export |
📊Sheets14 tools - ranges, tables, formatting, conditional rules |
🖼️Slides7 tools - create, batch update, thumbnails, comments |
📋Forms6 tools - build forms, publish, read responses |
✅Tasks6 tools - tasks & lists with hierarchy |
👤Contacts8 tools - people, groups, batch operations |
💬Chat6 tools - spaces, messages, search, reactions |
🔍Custom Search2 tools - programmable web search |
⚡Apps Script15 tools - write, deploy, run & debug scripts |
Each page lists every tool with its tier, parameters, required scopes, and example prompts. The complete reference covers all twelve in one place.
💬 Google Chat needs a one-time Chat app configuration and a Workspace account - see the Chat setup FAQ.
Quick Start
Set credentials → pick a launch command → connect your client. Full walkthrough with screenshots: workspacemcp.com/quick-start
You'll need an OAuth client from Google Cloud Console with the APIs enabled for the services you plan to use - the quick start guide walks through it in about five minutes.
|
Confidential Client # 1. Credentials
export GOOGLE_OAUTH_CLIENT_ID="..."
export GOOGLE_OAUTH_CLIENT_SECRET="..."
# 2. Launch - pick a tier
uvx workspace-mcp --tool-tier core # essential tools
uvx workspace-mcp --tool-tier extended # core + management ops
uvx workspace-mcp --tool-tier complete # everything
# Or cherry-pick services
uvx workspace-mcp --tools gmail drive calendar
|
OAuth 2.1 (PKCE) # 1. Credentials - MCP clients connect with PKCE and no
# secret, but Google still requires one server-side
export MCP_ENABLE_OAUTH21=true
export GOOGLE_OAUTH_CLIENT_ID="..."
export GOOGLE_OAUTH_CLIENT_SECRET="..."
export WORKSPACE_MCP_PORT=8000
export GOOGLE_OAUTH_REDIRECT_URI="http://localhost:${WORKSPACE_MCP_PORT}/oauth2callback"
export OAUTHLIB_INSECURE_TRANSPORT=1
# 2. Launch - OAuth 2.1 requires HTTP transport
uvx workspace-mcp --transport streamable-http --tool-tier core
|
Tool tiers keep context windows lean: core is the essential set, extended adds management operations, complete loads everything. Combine with --tools <service> ..., --read-only, or per-service --permissions, and subtract individual tools with --disabled-tools <name> ... - details in the server modes docs.
Connect Your Client
Claude Desktop, web & mobile - run the server in HTTP mode and add it as a Connector (Settings → Connectors → Add custom connector). This is the recommended path; the Connector guide has step-by-step screenshots. Legacy stdio configuration remains available for clients without Connector support - see the FAQ.
Claude Code
# Start the server in HTTP mode, then:
claude mcp add --transport http workspace-mcp http://localhost:8000/mcp
# Optional: install the bundled skill for better Workspace tool routing
ln -s "$(pwd)/skills/managing-google-workspace" ~/.claude/skills/managing-google-workspace
ChatGPT - connect via Developer Mode with the ChatGPT guide.
VS Code, LM Studio, Open WebUI, and everything else - any MCP client works over streamable HTTP (recommended) or stdio. Client-specific walkthroughs live in the guides and FAQ.
CLI
workspace-cli lists and calls tools against a running server with encrypted, disk-backed OAuth token caching - authenticate once, script forever:
uv run workspace-cli list
uv run workspace-cli call search_gmail_messages query="is:unread" max_results=5
Install globally with uv tool install . from this repo. ⚠️ Don't use uvx workspace-cli - an abandoned PyPI package squats that name.
Deployment & Advanced Configuration
Everything you need to run this in production lives in two places. The documentation covers auth modes and server configuration:
- OAuth 2.1 multi-user auth - bearer tokens, required for remote or shared HTTP endpoints
- Stateless container mode - zero disk writes for locked-down deployments
- OAuth proxy storage backends - memory, disk, or Valkey/Redis for distributed setups
- External OAuth provider mode - bring your own auth server, validate bearer tokens only
- Service accounts with domain-wide delegation - per-request user impersonation with an optional domain allowlist
- OpenTelemetry tracing - optional, off unless you configure an OTLP endpoint
- Docker -
docker build -t workspace-mcp . && docker run -p 8000:8000 workspace-mcp
The Advanced Deployment guide covers self-hosting specifics: reverse proxy setup with WORKSPACE_EXTERNAL_URL (including the nginx Origin: null consent workaround, the WORKSPACE_MCP_ALLOW_NULL_ORIGIN_CONSENT escape hatch, and the Referrer-Policy pitfall), origin validation and VS Code webview allowlisting, credential store backends (local directory or GCS with CMEK enforcement), and the complete environment variable reference.
Security Best Practices
By default this server sends no data anywhere except Google's APIs, using your own OAuth client credentials - no usage reporting, analytics, license server, or SaaS dependency. MIT licensed with no CLA, no dual licensing, and no copyleft in the dependency chain. The full security posture - scope minimization, sensitive-path blocking, stateless mode - is documented at workspacemcp.com.
A few things worth internalizing before you connect an LLM to your email:
- Prompt injection is real. Emails, docs, and events can contain hidden instructions. Only connect trusted data to an LLM, and be deliberate about which write tools you enable.
- Never commit
.env,client_secret.json, or.credentials/to source control. - Local file reads are sandboxed to the managed attachment directory. Broaden with
ALLOWED_FILE_DIRSonly if you trust the client and its data sources;.env*,~/.ssh/,~/.aws/, and similar paths are always blocked. - Production deployments should use HTTPS and OAuth 2.1.
Development
uv sync --group dev # install deps
uv run ruff check . # lint
uv run pytest # test
Single-file service modules live in g<service>/, tools are registered with @server.tool decorators, and tiers are defined in core/tool_tiers.yaml. PRs welcome.
License
MIT - see LICENSE. The license is 21 lines and says what it means.
Validations:
1 maintainer
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file workspace_mcp-1.24.1.tar.gz.
File metadata
- Download URL: workspace_mcp-1.24.1.tar.gz
- Upload date:
- Size: 404.5 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.2.0 CPython/3.11.13
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
8307e8b9b7c630ece3be2f22638e4eb00ad02b2a3624c5498994b707cf3da70b
|
|
| MD5 |
10ea406f2faf873cce8659f9c00bac94
|
|
| BLAKE2b-256 |
3fa259b570ed70f2bd4cc3aaa646285b54608de0af86e0399375a38a195d9cbf
|
File details
Details for the file workspace_mcp-1.24.1-py3-none-any.whl.
File metadata
- Download URL: workspace_mcp-1.24.1-py3-none-any.whl
- Upload date:
- Size: 419.7 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.2.0 CPython/3.11.13
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
75627429bae407ead89485327243975290fd335561ee19734b3c6fbd3e1d2c20
|
|
| MD5 |
6b165db0ae6a490e8041869aad481929
|
|
| BLAKE2b-256 |
08cd24a5aa9fa5007004718c014e9fa9d6d4b447aaf683434bab19140bae7a32
|
