Google Workspace MCP Server

Google Workspace MCP connects AI assistants, coding agents, and developer tools to Gmail, Google Drive, Calendar, Docs, Sheets, Slides, Forms, Chat, Apps Script, Tasks, Contacts, and Google Custom Search through one MCP server.

It provides deep read and write access across all 12 service groups, including fine-grained document editing, email and calendar management, file sharing, spreadsheet formatting, presentation creation, form responses, Chat spaces, Apps Script execution, and cross-service workflows. The same toolset is also available through a full-featured CLI for coding agents such as Claude Code and Codex.

Ready to connect your first client? Follow the interactive Quick Start Guide, or explore every tool and configuration option in the complete documentation.

What is Google Workspace MCP Server?

Google Workspace MCP Server is an open-source Model Context Protocol server that gives MCP-compatible clients a unified interface to Google Workspace. Instead of configuring a separate integration for every Google service, you can run one server and let an AI assistant securely search, read, create, edit, organize, and share Workspace content on behalf of the signed-in user.

The server works with free Google accounts and Google Workspace plans. It supports local use, direct CLI automation, and centrally hosted multi-user deployments with OAuth 2.1.

How to use Google Workspace MCP Server

The fastest path is the five-step Workspace MCP Quick Start, which walks through installation, Google OAuth setup, server startup, client connection, and validation.

You will need Python 3.10 or newer, uv/uvx, and a Google Cloud project with OAuth credentials. For a confidential OAuth client, a basic modern HTTP setup looks like this:

export GOOGLE_OAUTH_CLIENT_ID="your-client-id"
export GOOGLE_OAUTH_CLIENT_SECRET="your-client-secret"
export MCP_ENABLE_OAUTH21=true

uvx workspace-mcp --transport streamable-http --tool-tier core

Streamable HTTP is the recommended transport for modern MCP clients, OAuth 2.1, and multi-user deployments. Claude Desktop, Claude on the web, and Claude Cowork can connect through a custom Connector; Claude Code, VS Code, MCP Inspector, and other compatible clients can connect directly to the HTTP endpoint. Stdio remains available as a legacy fallback.

Start with the core tool tier, move to extended or complete when you need more operations, or load only selected services with --tools. Public PKCE clients, reverse proxies, and hosted deployments require additional authentication settings, so use the Quick Start Guide for setup and the authentication documentation for production configuration.

Key features of Google Workspace MCP Server

• 12 service groups in one server: Gmail, Drive, Calendar, Docs, Sheets, Slides, Forms, Chat, Apps Script, Tasks, Contacts, and Custom Search
• Deep Workspace operations: search, read, create, edit, format, comment, share, organize, send, publish, and automate
• Full CLI support: list and invoke tools directly from terminals, scripts, Claude Code, Codex, and other coding-agent workflows
• Modern authentication: OAuth 2.0, OAuth 2.1 with PKCE, automatic token refresh, multi-user bearer authentication, external OAuth providers, and service-account domain-wide delegation
• Flexible tool control: cumulative core, extended, and complete tiers, per-service selection, read-only mode, and granular permission levels
• Deployment-ready: streamable HTTP, stateless containers, reverse proxies, encrypted OAuth storage backends, and centrally hosted multi-user instances
• Private by default: uses your OAuth client and Google Cloud project; the default data path is directly from your infrastructure to Google APIs
• Open source: MIT licensed, with no license server, SaaS dependency, usage reporting, or analytics

See the complete Workspace MCP documentation for tool parameters, permission controls, authentication modes, environment variables, and deployment guidance.

Google Workspace MCP use cases

• Search Gmail for a conversation, save its attachments to Drive, and summarize the result in a Google Doc
• Find open Calendar time, create an event, add attendees, and attach relevant Drive files
• Create and format Docs, Sheets, Slides, and Forms from an AI assistant or coding agent
• Draft, send, label, and organize email while limiting the server to only the Gmail permissions you approve
• Manage Drive files, folders, shared drives, permissions, imports, exports, and shareable links
• Build Apps Script projects and execute cross-application Workspace automations
• Create internal assistants that work across company email, documents, tasks, contacts, calendars, and Chat spaces
• Run read-only research and reporting workflows with restricted OAuth scopes
• Host one secure OAuth 2.1 MCP endpoint for a team or an entire organization
• Use the CLI in scripts and coding-agent workflows without operating through a chat interface

Google Workspace MCP Server FAQ

What are the runtime requirements?

Google Workspace MCP requires Python 3.10 or newer, uv/uvx, and a Google Cloud project with OAuth credentials. You must enable the Google APIs for the services you plan to use. The Quick Start Guide walks through the complete setup.

Does the server send Workspace data to a third party?

By default, no. The server uses your own OAuth client and sends requests directly from your infrastructure to Google APIs on behalf of the authenticated user. There is no built-in analytics, usage reporting, license server, token relay, or required SaaS backend. Optional OpenTelemetry tracing remains disabled unless you install it and explicitly configure an OTLP endpoint.

How does authentication work?

You provide your own Google OAuth client. The server supports OAuth 2.0 for legacy local flows and OAuth 2.1 with PKCE and bearer tokens for modern or multi-user deployments. It also supports public PKCE clients without a Google client secret, external OAuth 2.1 providers, and service accounts with domain-wide delegation. Credential and OAuth-state storage can be configured for local disk, memory, GCS, or Valkey/Redis depending on the deployment.

Can I restrict what an AI assistant can access?

Yes. Use --read-only to request read-only scopes and remove write tools, select individual services with --tools, or apply per-service permission levels such as gmail:send or drive:readonly. Tool tiers provide another way to expose only the operations you need.

Can I host one server for my organization?

Yes. OAuth 2.1 multi-user authentication, stateless mode, external OAuth provider support, reverse-proxy configuration, and pluggable encrypted storage backends are designed for centralized deployments. You retain control of the infrastructure, OAuth client, scopes, credentials, and network path.

What transports are supported?

The server supports streamable HTTP and stdio. Streamable HTTP is recommended for modern clients and is required for OAuth 2.1. Stdio is retained as a legacy fallback for older or incomplete MCP clients.

Which Google accounts are supported?

The server supports free Google accounts and Google Workspace editions, including Starter, Standard, Plus, Enterprise, and Nonprofit plans. Some Google services have account-specific requirements; for example, Google Chat tools require a Workspace account and additional Chat app configuration.

Where can I find every available tool and parameter?

Browse the searchable Google Workspace MCP documentation for the full tool reference, examples, authentication settings, transport options, CLI usage, permissions, and deployment guides.

Get started with Google Workspace MCP

Connect your first AI client in five steps with the interactive Quick Start Guide. For advanced setup, production hosting, and the complete API reference, visit the Workspace MCP documentation.