Google Workspace Mcp

Google Workspace MCP Server

[](https://opensource.org/licenses/MIT) [](https://www.python.org/downloads/) [](https://pypi.org/project/workspace-mcp/) [](https://pepy.tech/projects/workspace-mcp) [](https://workspacemcp.com)

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 even dream of. With Remote OAuth2.1 multi-user support, fine-grained editing tools and the most extensive coverage of any Google Workspace tool in existance, Workspace MCP is in a different class. Offering native OAuth 2.1, stateless mode and external auth server 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.

---

⚡ Start

Quick Start · Prerequisites Google Cloud · Credentials

🧰 Tools

All Tools · Tool Tiers CLI · Start Server

🔌 Connect

Quick Start · Claude Desktop Claude Code · VS Code · LM Studio

🚀 Deploy

OAuth 2.1 · Stateless External OAuth · Reverse Proxy

📐 Develop

Architecture · Dev Setup Security · License

See it in action:

---

Overview

Workspace MCP is the single most complete MCP server, the only that integrates all major Google Workspace services with AI assistants and all agent platforms. The entire toolset is available for CLI usage supporting both local and remote instances.

Features

> 12 services  —  Gmail · Drive · Calendar · Docs · Sheets · Slides · Forms · Chat · Apps Script · Tasks · Contacts · Search

📧 Gmail — Complete email management, end-to-end coverage 📁 Drive — File operations with sharing, permissions, Office files, PDFs & images 📅 Calendar — Full event management with advanced features 📝 Docs — Deep, fine-grained editing, formatting & comments 📊 Sheets — Flexible cell management, formatting & conditional rules 🖼️ Slides — Presentation creation, updates & content manipulation 📋 Forms — Creation, publish settings & response management 💬 Chat — Space management, messaging & reactions

⚡ Apps Script — Cross-application workflow automation  Projects · deployments · versions · execution · debugging

✅ Tasks — Task & list management with hierarchy 👤 Contacts — People API with groups & batch operations 🔍 Custom Search — Programmable Search Engine integration

---

🔐 Authentication & Security OAuth 2.0 & 2.1 · auto token refresh · multi-user bearer tokens · transport-aware callbacks · CORS proxy

---

Security & Compliance

For Security Teams

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 telemetry, no usage reporting, no analytics, no license server, and no SaaS dependency. The entire data path is: your infrastructure → Google APIs.

• Fully open source — every line is auditable in this repo
• Your OAuth client, your GCP project — credentials never leave your environment
• You control the scopes — read-only, granular per-service permissions, or full access
• You control the network — deploy behind your reverse proxy, in your VPC, on your own terms
• No third-party services — no intermediary servers, no token relays, no hosted backends
• Stateless mode — zero disk writes for locked-down container environments
• Sensitive path blocking — local file reads default to the managed attachment directory, and validate_file_path() still blocks .env* files plus common home-directory credential stores such as ~/.ssh/ and ~/.aws/ even if ALLOWED_FILE_DIRS is broadened

Full dependency tree in pyproject.toml, pinned in uv.lock.

For Legal & Procurement

This project is [MIT licensed](LICENSE) — 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.

• Use commercially without restriction — build products, sell services, deploy internally
• Fork, embed, redistribute — MIT requires only attribution
• No CLA — contributions remain under MIT
• No telemetry to disclose — nothing to flag in a privacy review
• No network effects — the server never contacts any endpoint you didn't configure
• Standard dependency licenses — MIT, Apache 2.0, and BSD throughout the dependency chain; no copyleft, no AGPL

The license is 21 lines and says what it means.

---

Quick Start

> Set credentials → pick a launch command → connect your client

> 💡 New to Workspace MCP? Check out the Interactive Quick Start Guide → with step-by-step setup, screenshots, and troubleshooting tips!

Confidential Client Quick Start

# 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
uv run main.py --tools gmail drive calendar

Secretless / Public OAuth 2.1 (PKCE) Quick Start

# 1. Credentials
export MCP_ENABLE_OAUTH21=true
export GOOGLE_OAUTH_CLIENT_ID="..."
export WORKSPACE_MCP_PORT=8000
export GOOGLE_OAUTH_REDIRECT_URI="http://localhost:${WORKSPACE_MCP_PORT}/oauth2callback"
export OAUTHLIB_INSECURE_TRANSPORT=1
# Leave GOOGLE_OAUTH_CLIENT_SECRET unset for public PKCE clients
export FASTMCP_SERVER_AUTH_GOOGLE_JWT_SIGNING_KEY="$(openssl rand -hex 32)"

# 2. Launch — OAuth 2.1 requires HTTP transport
uvx workspace-mcp --transport streamable-http --tool-tier core
uvx workspace-mcp --transport streamable-http --tool-tier extended
uvx workspace-mcp --transport streamable-http --tool-tier complete

# Or cherry-pick services
uv run main.py --transport streamable-http --tools gmail drive calendar

[Credential setup →](#-credential-configuration) · [All launch options →](#start-the-server) · [Tier details →](#tool-tiers)

Environment Variable Reference

| Variable | | Purpose | |----------|:---:|---------| | 🔐 Authentication | | | | GOOGLE_OAUTH_CLIENT_ID | required | OAuth client ID from Google Cloud | | GOOGLE_OAUTH_CLIENT_SECRET | | OAuth client secret for confidential clients; optional for public OAuth 2.1 PKCE clients | | OAUTHLIB_INSECURE_TRANSPORT | required* | Set to 1 for development — allows http:// redirect | | USER_GOOGLE_EMAIL | | Default email for single-user auth | | GOOGLE_CLIENT_SECRET_PATH | | Custom path to client_secret.json | | GOOGLE_MCP_CREDENTIALS_DIR | | Credential directory — default ~/.google_workspace_mcp/credentials | | 🖥️ Server | | | | WORKSPACE_MCP_BASE_URI | | Base server URI (no port) — default http://localhost | | WORKSPACE_MCP_PORT | | Listening port — default 8000. Also controls the stdio-mode OAuth callback port. The PORT env var takes precedence if set. | | WORKSPACE_MCP_HOST | | Bind host — default 0.0.0.0 for OAuth 2.1 HTTP, 127.0.0.1 for legacy streamable HTTP. | | WORKSPACE_MCP_TRANSPORT | | stdio or streamable-http; used when --transport is not passed | | WORKSPACE_MCP_HTTP_PORT | | Advanced legacy-stdio sidecar /mcp port for local workspace-cli access. Disabled when empty. Binds to 127.0.0.1 only and is accessible to local processes. | | WORKSPACE_EXTERNAL_URL | | External URL for reverse proxy setups | | WORKSPACE_MCP_BRAND_NAME | | OAuth 2.1 consent-page server name — default FastMCP's name | | WORKSPACE_MCP_BRAND_ICON_URL | | OAuth 2.1 consent-page logo (hosted URL or data: URI), shown at 64px wide — default FastMCP's logo | | WORKSPACE_MCP_BRAND_WEBSITE_URL | | OAuth 2.1 consent-page website link | | WORKSPACE_ATTACHMENT_DIR | | Downloaded attachments dir and default trusted local attachment directory — default ~/.workspace-mcp/attachments/ | | WORKSPACE_MCP_URL | | Remote MCP endpoint URL for CLI | | ALLOWED_FILE_DIRS | | Colon-separated allowlist for local file reads | | 🧰 Tool Selection | | | | WORKSPACE_MCP_TOOLS | | Comma-separated services, e.g. gmail,drive,calendar; empty means all services | | WORKSPACE_MCP_TOOL_TIER | | core, extended, or complete; empty means all tools | | WORKSPACE_MCP_READ_ONLY | | true, 1, or yes to request read-only scopes and filter write tools | | WORKSPACE_MCP_PERMISSIONS | | Space-separated service:level entries, e.g. gmail:send drive:readonly; mutually exclusive with tools and read-only | | 🔑 OAuth 2.1 & Multi-User | | | | MCP_ENABLE_OAUTH21 | | true to enable OAuth 2.1 multi-user support. Required for remote or shared HTTP endpoints (--transport streamable-http); optional for local-only legacy HTTP, which binds to 127.0.0.1 by default. | | EXTERNAL_OAUTH21_PROVIDER | | true for external OAuth flow with bearer tokens | | WORKSPACE_MCP_STATELESS_MODE | | true for stateless container-friendly operation | | WORKSPACE_MCP_LOG_DIR | | Directory for mcp_server_debug.log — defaults to ~/.google_workspace_mcp/logs | | GOOGLE_OAUTH_REDIRECT_URI | | Override OAuth callback URL — default auto-constructed | | OAUTH_CUSTOM_REDIRECT_URIS | | Comma-separated additional redirect URIs | | OAUTH_ALLOWED_ORIGINS | | Comma-separated additional CORS origins | | WORKSPACE_MCP_OAUTH_PROXY_STORAGE_BACKEND | | memory, disk, or valkey — see [storage backends](#oauth-proxy-storage-backends) | | FASTMCP_SERVER_AUTH_GOOGLE_JWT_SIGNING_KEY | | Custom encryption key for OAuth proxy storage; required for public OAuth 2.1 clients when GOOGLE_OAUTH_CLIENT_SECRET is omitted | | WORKSPACE_MCP_ALLOWED_CLIENT_REDIRECT_URIS | | Comma-separated allowlist of redirect URIs that dynamically-registered OAuth clients may use. Default is unset (any URI permitted, per DCR). Supports FastMCP's glob patterns (*, *.example.com) | | 🗄️ Credential Store | | | | WORKSPACE_MCP_CREDENTIAL_STORE_BACKEND | | local_directory (default) or gcs — see [credential store system](#credential-store-system) | | WORKSPACE_MCP_CREDENTIALS_DIR | | Directory for the local_directory backend | | GOOGLE_MCP_CREDENTIALS_DIR | | Backward-compatible alias for WORKSPACE_MCP_CREDENTIALS_DIR | | WORKSPACE_MCP_GCS_BUCKET | | Required when backend is gcs — GCS bucket name | | WORKSPACE_MCP_GCS_PREFIX | | Optional object-name prefix for the gcs backend | | WORKSPACE_MCP_GCS_REQUIRE_CMEK | | true to require a bucket default KMS key at startup (fails fast if unset) | | 🔧 Service Account | | | | GOOGLE_SERVICE_ACCOUNT_KEY_FILE | | Path to service account JSON key file (domain-wide delegation) | | GOOGLE_SERVICE_ACCOUNT_KEY_JSON | | Inline service account JSON key (alternative to file) | | DWD_ALLOWED_DOMAINS | | Comma-separated domain allowlist for per-request impersonation (optional) | | 🔍 Custom Search | | | | GOOGLE_PSE_API_KEY | | API key for Programmable Search Engine | | GOOGLE_PSE_ENGINE_ID | | Search Engine ID for PSE |

*Required for development only. Claude Desktop stores credentials securely in the OS keychain — set them once in the extension pane.

---

Quick Start — Connect Claude to Google Workspace

The recommended setup is to run an instance and connect Claude to it via a Connector. Full instructions at workspacemcp.com/quick-start.

---

Prerequisites

Python 3.10+ · uv/uvx · Google Cloud Project with OAuth 2.0 credentials

If you want the GCS credential store backend, install the optional dependency first:

uv sync --extra gcs
# or
pip install "workspace-mcp[gcs]"

Configuration

Google Cloud Setup

1. Create Project — Open Console → → Create new project
2. Create OAuth Credentials — APIs & Services → Credentials → Create Credentials → OAuth Client ID

• Choose Desktop Application for a public PKCE client (no redirect URIs needed) or Web Application for a confidential client
• Download and note your Client ID and, if issued, Client Secret

1. Enable APIs — APIs & Services → Library, then enable each service:

| | | | | |:--|:--|:--|:--| | Calendar | Drive | Gmail | Docs | | Sheets | Slides | Forms | Tasks | | Chat | People | Custom Search | Apps Script |

> Google Chat needs extra setup. Enabling the API is not enough — you must also configure a Chat app and use a Workspace account. See [Chat setup](#-google-chat) under the tool list.

1. Set Credentials — see [Environment Variable Reference](#quick-start) above, or:

``bash export GOOGLE_OAUTH_CLIENT_ID="your-client-id" export GOOGLE_OAUTH_CLIENT_SECRET="your-secret" ` For public OAuth 2.1 PKCE clients, omit GOOGLEOAUTHCLIENTSECRET and set FASTMCPSERVERAUTHGOOGLEJWTSIGNING_KEY` instead.

Full OAuth documentation → · [Credential setup details →](#-credential-configuration)

Google Custom Search Setup

◆ Custom Search Configuration ← Enable web search capabilities

1. Create Search Engine

programmablesearchengine.google.com
/controlpanel/create

→ Configure sites or entire web
→ Note your Engine ID (cx)

Open Control Panel →

2. Get API Key

developers.google.com
/custom-search/v1/overview

→ Create/select project
→ Enable Custom Search API
→ Create credentials (API Key)

Get API Key →

3. Set Variables

export GOOGLE_PSE_API_KEY=\
  "your-api-key"
export GOOGLE_PSE_ENGINE_ID=\
  "your-engine-id"

Configure in environment

≡ Quick Setup Guide ← Step-by-step instructions

Complete Setup Process:

1. Create Search Engine - Visit the Control Panel

• Choose "Search the entire web" or specify sites
• Copy the Search Engine ID (looks like: 017643444788157684527:6ivsjbpxpqw)

1. Enable API & Get Key - Visit Google Developers Console

• Enable "Custom Search API" in your project
• Create credentials → API Key
• Restrict key to Custom Search API (recommende

…

Source & license

This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: taylorwilsdon
• Source: taylorwilsdon/googleworkspace_mcp
• License: MIT
• Homepage: https://workspacemcp.com

Install and usage instructions live in the source repository linked above.