Google Workspace Mcp
Control Gmail, Google Calendar, Docs, Sheets, Slides, Chat, Forms, Tasks, Search & Drive with AI - Comprehensive Google Workspace / G Suite MCP Server & CLI Tool
Last verified:
What is Google Workspace Mcp?
Google Workspace MCP Server is the most complete Model Context Protocol (MCP) server for Google Workspace, providing AI assistants with authenticated access to twelve integrated Google services. It offers over 100 tools across Gmail, Drive, Docs, Sheets, Slides, Forms, Calendar, Chat, Tasks, Contacts, Apps Script, and Google Custom Search through a single unified interface. The server acts as a secure bridge between AI agents and Google Workspace APIs, enabling natural language control of your entire Google Workspace environment.
Key features include OAuth 2.1 multi-user authentication with bearer tokens, three progressive tool tiers (core, extended, complete) for flexible deployment, read-only mode for safe operations, and a full CLI for coding agents like Claude Code and Codex. The server supports both streamable HTTP transport for modern clients and legacy stdio fallback. It is fully open source under the MIT License with no telemetry, analytics, or SaaS dependency—every request goes directly from your infrastructure to Google's APIs.
This tool is designed for developers building AI integrations, teams deploying AI assistants in production, and security-conscious organizations that need complete data sovereignty. It works with Claude Desktop, Claude web, VS Code, Gemini CLI, and other MCP clients. The self-hosted architecture ensures credentials never leave your environment, making it suitable for GDPR, HIPAA, and SOX compliance requirements.
Google Workspace Mcp pricing
Pricing model: Freemium
The Google Workspace MCP Server is 100% open source under the MIT License with no cost for self-hosted deployment. Users pay only for their own infrastructure. There is an optional managed cloud hosting option called Workspace MCP Cloud starting at $2/user/month with annual billing, which includes managed infrastructure, automatic upgrades, production/staging/sandbox environments, a shared Slack channel with maintainers, and quarterly reviews.
Google Workspace Mcp pros
- 100+ API tools across 12 Google services in one unified interface
- Fully open source under MIT License with no open-core gating
- OAuth 2.1 multi-user authentication with bearer token support
- No telemetry, analytics, license server, or SaaS dependency
- Direct data path from your infrastructure to Google APIs only
- Three progressive tool tiers (core, extended, complete) for scoping
- Read-only mode that requests only readonly scopes and disables write tools
- Full CLI mode for Claude Code, Codex, and scripting automation
- Stateless container mode with zero disk writes for locked-down deployments
- Pluggable OAuth storage backends (Memory, Disk, Valkey/Redis)
- Works with Claude Desktop, web, cowork, VS Code, and Gemini CLI
- Custom connector flow for Claude Desktop—no terminal or JSON editing required
- Granular per-service permission levels with --permissions flag
- Attachment storage with persistent local storage and HTTP exposure
- Reverse proxy support with external URL overrides for OAuth endpoints
Google Workspace Mcp cons
- Requires Python 3.10+ and uv/uvx for installation
- Users must create and manage their own Google OAuth client credentials
- Self-hosted—users responsible for deployment, maintenance, and security
- No official managed hosting in free tier (Cloud plans start at $2/user/month)
- OAuth 2.1 cannot be combined with --single-user mode
- stdio transport is legacy fallback not recommended for multi-user flows
- Web application OAuth clients require manual redirect URI configuration
- Requires Google Cloud project setup with APIs enabled
Frequently asked questions about Google Workspace Mcp
What is Google Workspace MCP Server?
Google Workspace MCP Server is an open-source Model Context Protocol server that provides authenticated access to Google Workspace APIs. It bridges AI assistants with twelve Google services (Gmail, Drive, Docs, Sheets, Slides, Forms, Calendar, Chat, Tasks, Contacts, Apps Script, and Custom Search), offering over 100 tools through a unified interface. Every request goes directly from your infrastructure to Google's APIs with no third-party processing.
How do I install Workspace MCP?
Install with uvx by running 'uvx workspace-mcp --tool-tier core' for the recommended core tier. You can also specify explicit services like 'uvx workspace-mcp --tools gmail drive calendar tasks'. The server requires Python 3.10+ and uv/uvx. Expand to extended or complete tiers when needed.
What OAuth client type should I use?
Use 'Desktop application' for local CLI and stdio-based setups. Use 'Web application' for hosted HTTP deployments, reverse proxies, and browser-based clients like Open WebUI. For Web application clients, your Google Cloud origins and redirect URIs must match the public URL users authenticate against. Desktop clients do not require manual redirect URI setup for standard local flows.
How do I connect to Claude Desktop?
Open Connectors in Claude, add a custom connector, and paste your MCP server URL. This OAuth sign-in flow handles everything without terminal or JSON editing. Alternatively, a .mcpb bundle is available from GitHub releases. The connector flow is the recommended path for Claude Desktop, web, and cowork.
What transport mode should I use?
Use streamable HTTP with '--transport streamable-http' for modern MCP clients and OAuth 2.1 support. This is the recommended mode for Claude Code, VS Code MCP, MCP Inspector, and multi-user flows. Keep stdio only as a legacy fallback for older clients with incomplete MCP support.
What are the tool tiers?
There are three cumulative tool tiers: core (recommended starting point), extended (adds more capabilities), and complete (all tools). You can start with '--tool-tier core' and expand when needed. Alternatively, use '--tools' to select explicit services like gmail, drive, calendar, tasks.
How do I enable read-only mode?
Use the '--read-only' flag to request only readonly scopes and disable write tools. This is useful for safe operations where AI should not modify data. You can also use '--permissions service:level' for granular per-service access levels like 'gmail:send'.
Is Workspace MCP secure?
Yes. Every request goes directly from your infrastructure to Google's APIs—no telemetry, analytics, license server, or SaaS dependency. Your OAuth credentials and GCP project stay in your environment. The server is fully open source and auditable, supports stateless mode with zero disk writes, blocks sensitive paths (.env, .ssh/, .aws/), and follows OAuth 2.1 with PKCE for secure authentication.
What MCP clients are supported?
Workspace MCP works with Claude Desktop (via custom connector), Claude web, cowork, Claude Code (via 'claude mcp add --transport http' command), VS Code (add server block to mcp.json), Gemini CLI, MCP Inspector, and any client supporting streamable HTTP with OAuth 2.1 bearer tokens.