by taylorwilsdon
Control Gmail, Google Calendar, Docs, Sheets, Slides, Chat, Forms, Tasks, Search, and Drive with AI. Comprehensive Googl
★ 1.7K
GitHub stars
Connects AI assistants to your entire Google Workspace account, letting you manage Gmail, Calendar, Drive, Docs, Sheets and other Google services through natural language commands.
Google Workspace MCP is a community-built MCP server published by taylorwilsdon that provides AI assistants with tools and capabilities via the Model Context Protocol. Control Gmail, Google Calendar, Docs, Sheets, Slides, Chat, Forms, Tasks, Search, and Drive with AI. Comprehensive Googl It is categorized under productivity, communication.
You can install Google Workspace MCP in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
Google Workspace MCP is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
Google Workspace MCP reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Google Workspace MCP is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
Google Workspace MCP has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
We wired Google Workspace MCP into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
We evaluated Google Workspace MCP against two servers with overlapping tools; this profile had the clearer scope statement.
Google Workspace MCP is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Google Workspace MCP is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
I recommend Google Workspace MCP for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Useful MCP listing: Google Workspace MCP is the kind of server we cite when onboarding engineers to host + tool permissions.
We evaluated Google Workspace MCP against two servers with overlapping tools; this profile had the clearer scope statement.
showing 1-10 of 53
| **@ Gmail** • **≡ Drive** • **⧖ Calendar** **≡ Docs** - Complete Gmail management, end-to-end coverage - Full calendar management with advanced features - File operations with Office format support - Document creation, editing & comments - Deep, exhaustive support for fine-grained editing --- **≡ Forms** • **@ Chat** • **≡ Sheets** • **≡ Slides** - Form creation, publish settings & response management - Space management & messaging capabilities - Spreadsheet operations with flexible cell management - Presentation creation, updates & content manipulation --- **◆ Apps Script** - Automate cross-application workflows with custom code - Execute existing business logic and custom functions - Manage script projects, deployments & versions - Debug and modify Apps Script code programmatically - Bridge Google Workspace services through automation | **⊠ Authentication & Security** - Advanced OAuth 2.0 & OAuth 2.1 support - Automatic token refresh & session management - Transport-aware callback handling - Multi-user bearer token authentication - Innovative CORS proxy architecture --- **✓ Tasks** • **👤 Contacts** • **◆ Custom Search** - Task & task list management with hierarchy - Contact management via People API with groups - Programmable Search Engine (PSE) integration |
| **Credentials** ```bash export GOOGLE_OAUTH_CLIENT_ID="..." export GOOGLE_OAUTH_CLIENT_SECRET="..." ``` [Full setup →](#credential-configuration) | **Launch Commands** ```bash uvx workspace-mcp --tool-tier core uv run main.py --tools gmail drive ``` [More options →](#start-the-server) | **Tool Tiers** - `core` - Essential tools - `extended` - Core + extras - `complete` - Everything [Details →](#tool-tiers) |
| **Required** | Variable | Purpose | |----------|---------| | `GOOGLE_OAUTH_CLIENT_ID` | OAuth client ID from Google Cloud | | `GOOGLE_OAUTH_CLIENT_SECRET` | OAuth client secret | | `OAUTHLIB_INSECURE_TRANSPORT=1` | Development only (allows `http://` redirect) | | **Optional** | Variable | Purpose | |----------|---------| | `USER_GOOGLE_EMAIL` | Default email for single-user auth | | `GOOGLE_PSE_API_KEY` | API key for Custom Search | | `GOOGLE_PSE_ENGINE_ID` | Search Engine ID for Custom Search | | `MCP_ENABLE_OAUTH21` | Set to `true` for OAuth 2.1 support | | `EXTERNAL_OAUTH21_PROVIDER` | Set to `true` for external OAuth flow with bearer tokens (requires OAuth 2.1) | | `WORKSPACE_MCP_STATELESS_MODE` | Set to `true` for stateless operation (requires OAuth 2.1) | |
| **1. Create Project** ```text console.cloud.google.com → Create new project → Note project name ``` [Open Console →](https://console.cloud.google.com/) | **2. OAuth Credentials** ```text APIs & Services → Credentials → Create Credentials → OAuth Client ID → Desktop Application ``` Download & save credentials | **3. Enable APIs** ```text APIs & Services → Library Search & enable: Calendar, Drive, Gmail, Docs, Sheets, Slides, Forms, Tasks, People, Chat, Search ``` See quick links below |
OAuth Credential Setup Guide ← Step-by-step instructions**Complete Setup Process:** 1. **Create OAuth 2.0 Credentials** - Visit [Google Cloud Console](https://console.cloud.google.com/) - Create a new project (or use existing) - Navigate to **APIs & Services → Credentials** - Click **Create Credentials → OAuth Client ID** - Choose **Desktop Application** as the application type (no redirect URIs needed!) - Download credentials and note the Client ID and Client Secret 2. **Enable Required APIs** - In **APIs & Services → Library** - Search for and enable each required API - Or use the quick links below for one-click enabling 3. **Configure Environment** - Set your credentials: ```bash export GOOGLE_OAUTH_CLIENT_ID="your-client-id" export GOOGLE_OAUTH_CLIENT_SECRET="your-secret" ``` [Full Documentation →](https://developers.google.com/workspace/guides/auth-overview) |
||
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.