# Google Workspace MCP Server [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT) [![Python 3.10+](https://img.shields.io/badge/Python-3.10%2B-blue.svg)](https://www.python.org/downloads/) [![PyPI](https://img.shields.io/pypi/v/workspace-mcp.svg)](https://pypi.org/project/workspace-mcp/) [![PyPI Downloads](https://static.pepy.tech/personalized-badge/workspace-mcp?period=total&units=INTERNATIONAL_SYSTEM&left_color=BLACK&right_color=BLUE&left_text=downloads)](https://pepy.tech/projects/workspace-mcp) [![Website](https://img.shields.io/badge/Website-workspacemcp.com-green.svg)](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 for use with tools like Claude Code and Codex!* **The most feature-complete Google Workspace MCP server**, with Remote OAuth2.1 multi-user support and 1-click Claude installation. With native OAuth 2.1, stateless mode and external auth server support, it's the only Workspace MCP you can host for your whole organization centrally & securely! ###### Support for all free Google accounts (Gmail, Docs, Drive etc) & 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.](https://workspacemcp.com/workspace-mcp-cloud)
---
⚑ Start
Quick Start Β· Prerequisites
Google Cloud · Credentials 		🧰 Tools
All Tools Β· Tool Tiers
CLI Β· Start Server 		πŸ”Œ Connect
1-Click Install Β· 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 that integrates all major Google Workspace services with AI assistants. It supports both single-user operation and multi-user authentication via OAuth 2.1, making it a powerful backend for custom applications. Built with FastMCP for optimal performance, featuring advanced authentication handling, service caching, and streamlined development patterns. The entire toolset is available for CLI usage supporting both local and remote instances. **Simplified Setup**: Now uses Google Desktop OAuth clients - no redirect URIs or port configuration needed! ## 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 formats
**πŸ“… 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** β€” `.env`, `.ssh/`, `.aws/`, and credential files are blocked regardless of configuration 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 β†’](https://workspacemcp.com/quick-start)** with step-by-step setup, screenshots, and troubleshooting tips!
```bash # 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 ``` [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` | **required** | OAuth client secret | | `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` | | `WORKSPACE_MCP_HOST` | | Bind host β€” default `0.0.0.0` | | `WORKSPACE_EXTERNAL_URL` | | External URL for reverse proxy setups | | `WORKSPACE_ATTACHMENT_DIR` | | Downloaded attachments dir β€” default `~/.workspace-mcp/attachments/` | | `WORKSPACE_MCP_URL` | | Remote MCP endpoint URL for CLI | | `ALLOWED_FILE_DIRS` | | Colon-separated allowlist for local file reads | | **πŸ”‘ OAuth 2.1 & Multi-User** | | | | `MCP_ENABLE_OAUTH21` | | `true` to enable OAuth 2.1 multi-user support | | `EXTERNAL_OAUTH21_PROVIDER` | | `true` for external OAuth flow with bearer tokens | | `WORKSPACE_MCP_STATELESS_MODE` | | `true` for stateless container-friendly operation | | `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 | | **πŸ”§ 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) | | **πŸ” 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.
--- ### One-Click Claude Desktop Install > `.dxt` bundles server, deps & manifest β€” download β†’ double-click β†’ done. No terminal, no JSON editing. 1. **Download** the latest `google_workspace_mcp.dxt` from [Releases](https://github.com/taylorwilsdon/google_workspace_mcp/releases) 2. **Install** β€” double-click the file, Claude Desktop prompts to install 3. **Configure** β€” Settings β†’ Extensions β†’ Google Workspace MCP, paste your OAuth credentials 4. **Use it** β€” start a new Claude chat and call any Google Workspace tool
--- ### Prerequisites **Python 3.10+** Β· **[uv/uvx](https://github.com/astral-sh/uv)** Β· **Google Cloud Project** with OAuth 2.0 credentials ### Configuration
Google Cloud Setup 1. **Create Project** β€” [Open Console β†’](https://console.cloud.google.com/) β†’ Create new project 2. **Create OAuth Credentials** β€” APIs & Services β†’ Credentials β†’ Create Credentials β†’ OAuth Client ID - Choose **Desktop Application** (no redirect URIs needed!) - Download and note your Client ID & Client Secret 3. **Enable APIs** β€” APIs & Services β†’ Library, then enable each service: | | | | | |:--|:--|:--|:--| | [Calendar](https://console.cloud.google.com/flows/enableapi?apiid=calendar-json.googleapis.com) | [Drive](https://console.cloud.google.com/flows/enableapi?apiid=drive.googleapis.com) | [Gmail](https://console.cloud.google.com/flows/enableapi?apiid=gmail.googleapis.com) | [Docs](https://console.cloud.google.com/flows/enableapi?apiid=docs.googleapis.com) | | [Sheets](https://console.cloud.google.com/flows/enableapi?apiid=sheets.googleapis.com) | [Slides](https://console.cloud.google.com/flows/enableapi?apiid=slides.googleapis.com) | [Forms](https://console.cloud.google.com/flows/enableapi?apiid=forms.googleapis.com) | [Tasks](https://console.cloud.google.com/flows/enableapi?apiid=tasks.googleapis.com) | | [Chat](https://console.cloud.google.com/flows/enableapi?apiid=chat.googleapis.com) | [People](https://console.cloud.google.com/flows/enableapi?apiid=people.googleapis.com) | [Custom Search](https://console.cloud.google.com/flows/enableapi?apiid=customsearch.googleapis.com) | [Apps Script](https://console.cloud.google.com/flows/enableapi?apiid=script.googleapis.com) | 4. **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" ``` [Full OAuth documentation β†’](https://developers.google.com/workspace/guides/auth-overview) Β· [Credential setup details β†’](#-credential-configuration)
### Google Custom Search Setup
β—† Custom Search Configuration ← Enable web search capabilities
**1. Create Search Engine** ```text programmablesearchengine.google.com /controlpanel/create β†’ Configure sites or entire web β†’ Note your Engine ID (cx) ``` [Open Control Panel β†’](https://programmablesearchengine.google.com/controlpanel/create) **2. Get API Key** ```text developers.google.com /custom-search/v1/overview β†’ Create/select project β†’ Enable Custom Search API β†’ Create credentials (API Key) ``` [Get API Key β†’](https://developers.google.com/custom-search/v1/overview) **3. Set Variables** ```bash 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](https://programmablesearchengine.google.com/controlpanel/create) - Choose "Search the entire web" or specify sites - Copy the Search Engine ID (looks like: `017643444788157684527:6ivsjbpxpqw`) 2. **Enable API & Get Key** - Visit [Google Developers Console](https://console.cloud.google.com/) - Enable "Custom Search API" in your project - Create credentials β†’ API Key - Restrict key to Custom Search API (recommended) 3. **Configure Environment** - Add to your shell or `.env`: ```bash export GOOGLE_PSE_API_KEY="AIzaSy..." export GOOGLE_PSE_ENGINE_ID="01764344478..." ``` ≑ [Full Documentation β†’](https://developers.google.com/custom-search/v1/overview)
### Start the Server > **πŸ“Œ Transport Mode Guidance**: Use **streamable HTTP mode** (`--transport streamable-http`) for all modern MCP clients including Claude Code, VS Code MCP, and MCP Inspector. Stdio mode is only for clients with incomplete MCP specification support.
β–Ά Launch Commands ← Choose your startup mode
**β–Ά Legacy Mode** ```bash uv run main.py ``` ⚠️ Stdio mode (incomplete MCP clients only) **β—† HTTP Mode (Recommended)** ```bash uv run main.py \ --transport streamable-http ``` βœ… Full MCP spec compliance & OAuth 2.1 **@ Single User** ```bash uv run main.py \ --single-user ``` Simplified authentication ⚠️ Cannot be used with OAuth 2.1 mode
β—† Advanced Options ← Tool selection, tiers & Docker **β–Ά Selective Tool Loading** ```bash # Load specific services only uv run main.py --tools gmail drive calendar uv run main.py --tools sheets docs # Combine with other flags uv run main.py --single-user --tools gmail ``` **πŸ”’ Read-Only Mode** ```bash # Requests only read-only scopes & disables write tools uv run main.py --read-only # Combine with specific tools or tiers uv run main.py --tools gmail drive --read-only uv run main.py --tool-tier core --read-only ``` Read-only mode provides secure, restricted access by: - Requesting only `*.readonly` OAuth scopes (e.g., `gmail.readonly`, `drive.readonly`) - Automatically filtering out tools that require write permissions at startup - Allowing read operations: list, get, search, and export across all services **πŸ” Granular Permissions** ```bash # Per-service permission levels uv run main.py --permissions gmail:organize drive:readonly # Combine permissions with tier filtering uv run main.py --permissions gmail:send drive:full --tool-tier core ``` Granular permissions mode provides service-by-service scope control: - Format: `service:level` (one entry per service) - Gmail levels: `readonly`, `organize`, `drafts`, `send`, `full` (cumulative) - Tasks levels: `readonly`, `manage`, `full` (cumulative; `manage` allows create/update/move but denies `delete` and `clear_completed`) - Other services currently support: `readonly`, `full` - `--permissions` and `--read-only` are mutually exclusive - `--permissions` cannot be combined with `--tools`; enabled services are determined by the `--permissions` entries (optionally filtered by `--tool-tier`) - With `--tool-tier`, only tier-matched tools are enabled and only services that have tools in the selected tier are imported **β˜… Tool Tiers** ```bash uv run main.py --tool-tier core # ● Essential tools only uv run main.py --tool-tier extended # ◐ Core + additional uv run main.py --tool-tier complete # β—‹ All available tools ``` **β—† Docker Deployment** ```bash docker build -t workspace-mcp . docker run -p 8000:8000 -v $(pwd):/app \ workspace-mcp --transport streamable-http # With tool selection via environment variables docker run -e TOOL_TIER=core workspace-mcp docker run -e TOOLS="gmail drive calendar" workspace-mcp ``` **Available Services**: `gmail` β€’ `drive` β€’ `calendar` β€’ `docs` β€’ `sheets` β€’ `forms` β€’ `tasks` β€’ `contacts` β€’ `chat` β€’ `search`
### CLI The `workspace-cli` command lists tools and calls them against a running server β€” with encrypted, disk-backed OAuth token caching so you only authenticate once. On first run it opens a browser for Google consent; subsequent runs reuse the cached tokens automatically. Tokens are stored encrypted at `~/.workspace-mcp/cli-tokens/` using a Fernet key auto-generated at `~/.workspace-mcp/.cli-encryption-key`.
β–Ά workspace-cli Commands ← Persistent OAuth, no re-auth on every call
**β–Ά List Tools** ```bash uv run workspace-cli list uv run workspace-cli --url https://custom.server/mcp list # Or, if installed globally: workspace-cli list workspace-cli --url https://custom.server/mcp list ``` View all available tools **β—† Call a Tool** ```bash uv run workspace-cli call search_gmail_messages \ query="is:unread" max_results=5 ``` Execute a tool with key=value arguments
Set URL for remote endpoints with `--url` or the `WORKSPACE_MCP_URL` environment variable.
≑ Advanced: FastMCP CLI ← inspect, install, discover The upstream [FastMCP CLI](https://gofastmcp.com/cli) is also bundled and provides additional commands for schema inspection, client installation, and editor discovery. Note that `fastmcp` uses in-memory token storage, so each invocation may re-trigger the OAuth flow. ```bash fastmcp inspect fastmcp_server.py # print tools, resources, prompts fastmcp install claude-code fastmcp_server.py # one-command client setup fastmcp install cursor fastmcp_server.py fastmcp discover # find servers configured in editors ``` See `fastmcp --help` or the [FastMCP CLI docs](https://gofastmcp.com/cli) for the full command reference.
### Tool Tiers The server organizes tools into **three progressive tiers** for simplified deployment. Choose a tier that matches your usage needs and API quota requirements.
#### Available Tiers **● Core** (`--tool-tier core`) Essential tools for everyday tasks. Perfect for light usage with minimal API quotas. Includes search, read, create, and basic modify operations across all services. **● Extended** (`--tool-tier extended`) Core functionality plus management tools. Adds labels, folders, batch operations, and advanced search. Ideal for regular usage with moderate API needs. **● Complete** (`--tool-tier complete`) Full API access including comments, headers/footers, publishing settings, and administrative functions. For power users needing maximum functionality. #### Important Notes β–Ά **Start with `core`** and upgrade as needed β–Ά **Tiers are cumulative** – each includes all previous β–Ά **Mix and match** with `--tools` for specific services β–Ά **Configuration** in `core/tool_tiers.yaml` β–Ά **Authentication** included in all tiers
#### Usage Examples ```bash # Basic tier selection uv run main.py --tool-tier core # Start with essential tools only uv run main.py --tool-tier extended # Expand to include management features uv run main.py --tool-tier complete # Enable all available functionality # Selective service loading with tiers uv run main.py --tools gmail drive --tool-tier core # Core tools for specific services uv run main.py --tools gmail --tool-tier extended # Extended Gmail functionality only uv run main.py --tools docs sheets --tool-tier complete # Full access to Docs and Sheets # Combine tier selection with granular permission levels uv run main.py --permissions gmail:organize drive:full --tool-tier core ``` ## πŸ“‹ Credential Configuration
πŸ”‘ OAuth Credentials Setup ← Essential for all installations
**πŸš€ Environment Variables** ```bash export GOOGLE_OAUTH_CLIENT_ID=\ "your-client-id" export GOOGLE_OAUTH_CLIENT_SECRET=\ "your-secret" ``` Best for production **πŸ“ File-based** ```bash # Download & place in project root client_secret.json # Or specify custom path export GOOGLE_CLIENT_SECRET_PATH=\ /path/to/secret.json ``` Traditional method **⚑ .env File** ```bash cp .env.oauth21 .env # Edit .env with credentials ``` Best for development
πŸ“– Credential Loading Details ← Understanding priority & best practices **Loading Priority** 1. Environment variables (`export VAR=value`) 2. `.env` file in project root (warning - if you run via `uvx` rather than `uv run` from the repo directory, you are spawning a standalone process not associated with your clone of the repo and it will not find your .env file without specifying it directly) 3. `client_secret.json` via `GOOGLE_CLIENT_SECRET_PATH` 4. Default `client_secret.json` in project root **Why Environment Variables?** - βœ… **Docker/K8s ready** - Native container support - βœ… **Cloud platforms** - Heroku, Railway, Vercel - βœ… **CI/CD pipelines** - GitHub Actions, Jenkins - βœ… **No secrets in git** - Keep credentials secure - βœ… **Easy rotation** - Update without code changes
--- ## 🧰 Available Tools > **Note**: All tools support automatic authentication via `@require_google_service()` decorators with 30-minute service caching.
> πŸ“– **Looking for detailed parameters?** Visit the **[Complete Documentation β†’](https://workspacemcp.com/docs)** for comprehensive tool reference, examples, and API guides!
#### πŸ“… Google Calendar [`calendar_tools.py`](gcalendar/calendar_tools.py) | Tool | Tier | Description | |------|------|-------------| | `list_calendars` | Core | List accessible calendars | | `get_events` | Core | Retrieve events with time range filtering | | `manage_event` | Core | Create, update, or delete calendar events | | `create_calendar` | Extended | Create a new secondary Google Calendar | | `query_freebusy` | Extended | Query free/busy information for calendars | | `manage_out_of_office` | Extended | Create, list, update, or delete Out of Office events | | `manage_focus_time` | Extended | Create, list, update, or delete Focus Time events | #### πŸ“ Google Drive [`drive_tools.py`](gdrive/drive_tools.py) | Tool | Tier | Description | |------|------|-------------| | `search_drive_files` | Core | Search files with query syntax | | `get_drive_file_content` | Core | Read file content (Office formats) | | `get_drive_file_download_url` | Core | Download Drive files to local disk | | `create_drive_file` | Core | Create files or fetch from URLs | | `create_drive_folder` | Core | Create empty folders in Drive or shared drives | | `import_to_google_doc` | Core | Import files (MD, DOCX, HTML, etc.) as Google Docs | | `get_drive_shareable_link` | Core | Get shareable links for a file | | `list_drive_items` | Extended | List folder contents | | `copy_drive_file` | Extended | Copy existing files (templates) with optional renaming | | `update_drive_file` | Extended | Update file metadata, move between folders | | `manage_drive_access` | Extended | Grant, update, revoke permissions, and transfer ownership | | `set_drive_file_permissions` | Extended | Set link sharing and file-level sharing settings | | `get_drive_file_permissions` | Complete | Get detailed file permissions | | `check_drive_file_public_access` | Complete | Check public sharing status | #### πŸ“§ Gmail [`gmail_tools.py`](gmail/gmail_tools.py) | Tool | Tier | Description | |------|------|-------------| | `search_gmail_messages` | Core | Search with Gmail operators | | `get_gmail_message_content` | Core | Retrieve message content | | `get_gmail_messages_content_batch` | Core | Batch retrieve message content | | `send_gmail_message` | Core | Send emails | | `get_gmail_thread_content` | Extended | Get full thread content | | `modify_gmail_message_labels` | Extended | Modify message labels | | `list_gmail_labels` | Extended | List available labels | | `list_gmail_filters` | Extended | List Gmail filters | | `manage_gmail_label` | Extended | Create/update/delete labels | | `manage_gmail_filter` | Extended | Create or delete Gmail filters | | `draft_gmail_message` | Extended | Create drafts | | `get_gmail_threads_content_batch` | Complete | Batch retrieve thread content | | `batch_modify_gmail_message_labels` | Complete | Batch modify labels | | `start_google_auth` | Complete | Legacy OAuth 2.0 auth (disabled when OAuth 2.1 is enabled) |
πŸ“Ž Email Attachments ← Send emails with files Both `send_gmail_message` and `draft_gmail_message` support attachments via two methods: **Option 1: File Path** (local server only) ```python attachments=[{"path": "/path/to/report.pdf"}] ``` Reads file from disk, auto-detects MIME type. Optional `filename` override. **Option 2: Base64 Content** (works everywhere) ```python attachments=[{ "filename": "report.pdf", "content": "JVBERi0xLjQK...", # base64-encoded "mime_type": "application/pdf" # optional }] ``` **⚠️ Centrally Hosted Servers**: When the MCP server runs remotely (cloud, shared instance), it cannot access your local filesystem. Use **Option 2** with base64-encoded content. Your MCP client must encode files before sending.
πŸ“₯ Downloaded Attachment Storage ← Where downloaded files are saved When downloading Gmail attachments (`get_gmail_attachment_content`) or Drive files (`get_drive_file_download_url`), files are saved to a persistent local directory rather than a temporary folder in the working directory. **Default location:** `~/.workspace-mcp/attachments/` Files are saved with their original filename plus a short UUID suffix for uniqueness (e.g., `invoice_a1b2c3d4.pdf`). In **stdio mode**, the tool returns the absolute file path for direct filesystem access. In **HTTP mode**, it returns a download URL via the `/attachments/{file_id}` endpoint. To customize the storage directory: ```bash export WORKSPACE_ATTACHMENT_DIR="/path/to/custom/dir" ``` Saved files expire after 1 hour and are cleaned up automatically.
#### πŸ“ Google Docs [`docs_tools.py`](gdocs/docs_tools.py) | Tool | Tier | Description | |------|------|-------------| | `get_doc_content` | Core | Extract document text | | `create_doc` | Core | Create new documents | | `modify_doc_text` | Core | Insert, replace, and richly format text with tab/segment targeting, append-to-segment support, advanced typography, and link management | | `search_docs` | Extended | Find documents by name | | `find_and_replace_doc` | Extended | Find and replace text | | `list_docs_in_folder` | Extended | List docs in folder | | `insert_doc_elements` | Extended | Add tables, lists, page breaks | | `update_paragraph_style` | Extended | Apply advanced paragraph styling including headings, spacing, direction, pagination controls, shading, and bulleted/numbered/checkbox lists with nesting | | `get_doc_as_markdown` | Extended | Export document as formatted Markdown with optional comments | | `insert_doc_image` | Complete | Insert images from Drive/URLs | | `update_doc_headers_footers` | Complete | Create or update headers and footers with correct segment-aware writes | | `batch_update_doc` | Complete | Execute atomic multi-step Docs API operations including named ranges, section breaks, document/section layout, header/footer creation, segment-aware inserts, images, tables, and rich formatting | | `inspect_doc_structure` | Complete | Analyze document structure, including safe insertion points, tables, section breaks, headers/footers, and named ranges | | `export_doc_to_pdf` | Extended | Export document to PDF | | `create_table_with_data` | Complete | Create data tables | | `debug_table_structure` | Complete | Debug table issues | | `list_document_comments` | Complete | List all document comments | | `manage_document_comment` | Complete | Create, reply to, or resolve comments | #### πŸ“Š Google Sheets [`sheets_tools.py`](gsheets/sheets_tools.py) | Tool | Tier | Description | |------|------|-------------| | `read_sheet_values` | Core | Read cell ranges | | `modify_sheet_values` | Core | Write/update/clear cells | | `create_spreadsheet` | Core | Create new spreadsheets | | `list_spreadsheets` | Extended | List accessible spreadsheets | | `get_spreadsheet_info` | Extended | Get spreadsheet metadata | | `format_sheet_range` | Extended | Apply colors, number formats, text wrapping, alignment, bold/italic, font size | | `list_sheet_tables` | Extended | List structured tables with IDs, names, ranges, and columns | | `create_sheet` | Complete | Add sheets to existing files | | `append_table_rows` | Complete | Append rows to a structured table, auto-extending the table range | | `list_spreadsheet_comments` | Complete | List all spreadsheet comments | | `manage_spreadsheet_comment` | Complete | Create, reply to, or resolve comments | | `manage_conditional_formatting` | Complete | Add, update, or delete conditional formatting rules | #### πŸ–ΌοΈ Google Slides [`slides_tools.py`](gslides/slides_tools.py) | Tool | Tier | Description | |------|------|-------------| | `create_presentation` | Core | Create new presentations | | `get_presentation` | Core | Retrieve presentation details | | `batch_update_presentation` | Extended | Apply multiple updates | | `get_page` | Extended | Get specific slide information | | `get_page_thumbnail` | Extended | Generate slide thumbnails | | `list_presentation_comments` | Complete | List all presentation comments | | `manage_presentation_comment` | Complete | Create, reply to, or resolve comments | #### πŸ“‹ Google Forms [`forms_tools.py`](gforms/forms_tools.py) | Tool | Tier | Description | |------|------|-------------| | `create_form` | Core | Create new forms | | `get_form` | Core | Retrieve form details & URLs | | `set_publish_settings` | Complete | Configure form settings | | `get_form_response` | Complete | Get individual responses | | `list_form_responses` | Extended | List all responses with pagination | | `batch_update_form` | Complete | Apply batch updates (questions, settings) | #### βœ“ Google Tasks [`tasks_tools.py`](gtasks/tasks_tools.py) | Tool | Tier | Description | |------|------|-------------| | `list_tasks` | Core | List tasks with filtering | | `get_task` | Core | Retrieve task details | | `manage_task` | Core | Create, update, delete, or move tasks | | `list_task_lists` | Complete | List task lists | | `get_task_list` | Complete | Get task list details | | `manage_task_list` | Complete | Create, update, delete task lists, or clear completed tasks | #### πŸ‘€ Google Contacts [`contacts_tools.py`](gcontacts/contacts_tools.py) | Tool | Tier | Description | |------|------|-------------| | `search_contacts` | Core | Search contacts by name, email, phone | | `get_contact` | Core | Retrieve detailed contact info | | `list_contacts` | Core | List contacts with pagination | | `manage_contact` | Core | Create, update, or delete contacts | | `list_contact_groups` | Extended | List contact groups/labels | | `get_contact_group` | Extended | Get group details with members | | `manage_contacts_batch` | Complete | Batch create, update, or delete contacts | | `manage_contact_group` | Complete | Create, update, delete groups, or modify membership | #### πŸ’¬ Google Chat [`chat_tools.py`](gchat/chat_tools.py) | Tool | Tier | Description | |------|------|-------------| | `list_spaces` | Extended | List chat spaces/rooms | | `get_messages` | Core | Retrieve space messages | | `send_message` | Core | Send messages to spaces | | `search_messages` | Core | Search across chat history | | `create_reaction` | Core | Add emoji reaction to a message | | `download_chat_attachment` | Extended | Download attachment from a chat message | #### πŸ” Google Custom Search [`search_tools.py`](gsearch/search_tools.py) | Tool | Tier | Description | |------|------|-------------| | `search_custom` | Core | Perform web searches (supports site restrictions via sites parameter) | | `get_search_engine_info` | Complete | Retrieve search engine metadata | #### ⚑ Google Apps Script [`apps_script_tools.py`](gappsscript/apps_script_tools.py) | Tool | Tier | Description | |------|------|-------------| | `list_script_projects` | Core | List accessible Apps Script projects | | `get_script_project` | Core | Get complete project with all files | | `get_script_content` | Core | Retrieve specific file content | | `create_script_project` | Core | Create new standalone or bound project | | `update_script_content` | Core | Update or create script files | | `run_script_function` | Core | Execute function with parameters | | `list_deployments` | Extended | List all project deployments | | `manage_deployment` | Extended | Create, update, or delete script deployments | | `list_script_processes` | Extended | View recent executions and status | **Tool Tier Legend:**
● **Core** β€” Essential tools for basic functionality Β· Minimal API usage Β· Getting started
● **Extended** β€” Core + additional features Β· Regular usage Β· Expanded capabilities
● **Complete** β€” All available tools including advanced features Β· Power users Β· Full API access --- ### Connect to Claude Desktop The server supports two transport modes: #### Stdio Mode (Legacy - For Clients with Incomplete MCP Support) > **⚠️ Important**: Stdio mode is a **legacy fallback** for clients that don't properly implement the MCP specification with OAuth 2.1 and streamable HTTP support. **Claude Code and other modern MCP clients should use streamable HTTP mode** (`--transport streamable-http`) for proper OAuth flow and multi-user support. In general, you should use the one-click DXT installer package for Claude Desktop. If you are unable to for some reason, you can configure it manually via `claude_desktop_config.json` **Manual Claude Configuration (Alternative)**
πŸ“ Claude Desktop JSON Config ← Click for manual setup instructions 1. Open Claude Desktop Settings β†’ Developer β†’ Edit Config - **macOS**: `~/Library/Application Support/Claude/claude_desktop_config.json` - **Windows**: `%APPDATA%\Claude\claude_desktop_config.json` 2. Add the server configuration: ```json { "mcpServers": { "google_workspace": { "command": "uvx", "args": ["workspace-mcp"], "env": { "GOOGLE_OAUTH_CLIENT_ID": "your-client-id", "GOOGLE_OAUTH_CLIENT_SECRET": "your-secret", "OAUTHLIB_INSECURE_TRANSPORT": "1" } } } } ```
### Connect to LM Studio Add a new MCP server in LM Studio (Settings β†’ MCP Servers) using the same JSON format: ```json { "mcpServers": { "google_workspace": { "command": "uvx", "args": ["workspace-mcp"], "env": { "GOOGLE_OAUTH_CLIENT_ID": "your-client-id", "GOOGLE_OAUTH_CLIENT_SECRET": "your-secret", "OAUTHLIB_INSECURE_TRANSPORT": "1", } } } } ``` ### 2. Advanced / Cross-Platform Installation If you’re developing, deploying to servers, or using another MCP-capable client, keep reading. #### Instant CLI (uvx)
⚑ Quick Start with uvx ← No installation required! ```bash # Requires Python 3.10+ and uvx # First, set credentials (see Credential Configuration above) uvx workspace-mcp --tool-tier core # or --tools gmail drive calendar ``` > **Note**: Configure [OAuth credentials](#credential-configuration) before running. Supports environment variables, `.env` file, or `client_secret.json`.
### Local Development Setup
πŸ› οΈ Developer Workflow ← Install deps, lint, and test ```bash # Install everything needed for linting, tests, and release tooling uv sync --group dev # Run the same linter that git hooks invoke automatically uv run ruff check . # Execute the full test suite (async fixtures require pytest-asyncio) uv run pytest ``` - `uv sync --group test` installs only the testing stack if you need a slimmer environment. - `uv run main.py --transport streamable-http` launches the server with your checked-out code for manual verification. - Ruff is part of the `dev` group because pre-push hooks call `ruff check` automaticallyβ€”run it locally before committing to avoid hook failures.
### OAuth 2.1 Support (Multi-User Bearer Token Authentication) The server includes OAuth 2.1 support for bearer token authentication, enabling multi-user session management. **OAuth 2.1 automatically reuses your existing `GOOGLE_OAUTH_CLIENT_ID` and `GOOGLE_OAUTH_CLIENT_SECRET` credentials** - no additional configuration needed! **When to use OAuth 2.1:** - Multiple users accessing the same MCP server instance - Need for bearer token authentication instead of passing user emails - Building web applications or APIs on top of the MCP server - Production environments requiring secure session management - Browser-based clients requiring CORS support **⚠️ Important: Mutually exclusive authentication modes** OAuth 2.1 mode (`MCP_ENABLE_OAUTH21=true`) cannot be used together with `--single-user` or service account mode: - **Single-user mode**: For legacy clients that pass user emails in tool calls - **OAuth 2.1 mode**: For modern multi-user scenarios with bearer token authentication - **Service account mode**: For headless/server-to-server use via domain-wide delegation Choose one authentication method - combining incompatible modes will result in a startup error. **Enabling OAuth 2.1:** To enable OAuth 2.1, set the `MCP_ENABLE_OAUTH21` environment variable to `true`. ```bash # OAuth 2.1 requires HTTP transport mode export MCP_ENABLE_OAUTH21=true uv run main.py --transport streamable-http ``` If `MCP_ENABLE_OAUTH21` is not set to `true`, the server will use legacy authentication, which is suitable for clients that do not support OAuth 2.1.
πŸ” How the FastMCP GoogleProvider handles OAuth ← Advanced OAuth 2.1 details FastMCP ships a native `GoogleProvider` that we now rely on directly. It solves the two tricky parts of using Google OAuth with MCP clients: 1. **Dynamic Client Registration**: Google still doesn't support OAuth 2.1 DCR, but the FastMCP provider exposes the full DCR surface and forwards registrations to Google using your fixed credentials. MCP clients register as usual and the provider hands them your Google client ID/secret under the hood. 2. **CORS & Browser Compatibility**: The provider includes an OAuth proxy that serves all discovery, authorization, and token endpoints with proper CORS headers. We no longer maintain custom `/oauth2/*` routesβ€”the provider handles the upstream exchanges securely and advertises the correct metadata to clients. The result is a leaner server that still enables any OAuth 2.1 compliant client (including browser-based ones) to authenticate through Google without bespoke code.
### Stateless Mode (Container-Friendly) The server supports a stateless mode designed for containerized environments where file system writes should be avoided: **Enabling Stateless Mode:** ```bash # Stateless mode requires OAuth 2.1 to be enabled export MCP_ENABLE_OAUTH21=true export WORKSPACE_MCP_STATELESS_MODE=true uv run main.py --transport streamable-http ``` **Key Features:** - **No file system writes**: Credentials are never written to disk - **No debug logs**: File-based logging is completely disabled - **Memory-only sessions**: All tokens stored in memory via OAuth 2.1 session store - **Container-ready**: Perfect for Docker, Kubernetes, and serverless deployments - **Token per request**: Each request must include a valid Bearer token **Requirements:** - Must be used with `MCP_ENABLE_OAUTH21=true` - Incompatible with single-user mode - Clients must handle OAuth flow and send valid tokens with each request This mode is ideal for: - Cloud deployments where persistent storage is unavailable - Multi-tenant environments requiring strict isolation - Containerized applications with read-only filesystems - Serverless functions and ephemeral compute environments **MCP Inspector**: No additional configuration needed with desktop OAuth client. **Claude Code**: No additional configuration needed with desktop OAuth client. ### OAuth Proxy Storage Backends The server supports pluggable storage backends for OAuth proxy state management via FastMCP 2.13.0+. Choose a backend based on your deployment needs. **Available Backends:** | Backend | Best For | Persistence | Multi-Server | |---------|----------|-------------|--------------| | Memory | Development, testing | ❌ | ❌ | | Disk | Single-server production | βœ… | ❌ | | Valkey/Redis | Distributed production | βœ… | βœ… | **Configuration:** ```bash # Memory storage (fast, no persistence) export WORKSPACE_MCP_OAUTH_PROXY_STORAGE_BACKEND=memory # Disk storage (persists across restarts) export WORKSPACE_MCP_OAUTH_PROXY_STORAGE_BACKEND=disk export WORKSPACE_MCP_OAUTH_PROXY_DISK_DIRECTORY=~/.fastmcp/oauth-proxy # Valkey/Redis storage (distributed, multi-server) export WORKSPACE_MCP_OAUTH_PROXY_STORAGE_BACKEND=valkey export WORKSPACE_MCP_OAUTH_PROXY_VALKEY_HOST=redis.example.com export WORKSPACE_MCP_OAUTH_PROXY_VALKEY_PORT=6379 ``` > Disk support requires `workspace-mcp[disk]` (or `py-key-value-aio[disk]`) when installing from source. > The official Docker image includes the `disk` extra by default. > Valkey support is optional. Install `workspace-mcp[valkey]` (or `py-key-value-aio[valkey]`) only if you enable the Valkey backend. > Windows: building `valkey-glide` from source requires MSVC C++ build tools with C11 support. If you see `aws-lc-sys` C11 errors, set `CFLAGS=/std:c11`.
πŸ” Valkey/Redis Configuration Options | Variable | Default | Description | |----------|---------|-------------| | `WORKSPACE_MCP_OAUTH_PROXY_VALKEY_HOST` | localhost | Valkey/Redis host | | `WORKSPACE_MCP_OAUTH_PROXY_VALKEY_PORT` | 6379 | Port (6380 auto-enables TLS) | | `WORKSPACE_MCP_OAUTH_PROXY_VALKEY_DB` | 0 | Database number | | `WORKSPACE_MCP_OAUTH_PROXY_VALKEY_USE_TLS` | auto | Enable TLS (auto if port 6380) | | `WORKSPACE_MCP_OAUTH_PROXY_VALKEY_USERNAME` | - | Authentication username | | `WORKSPACE_MCP_OAUTH_PROXY_VALKEY_PASSWORD` | - | Authentication password | | `WORKSPACE_MCP_OAUTH_PROXY_VALKEY_REQUEST_TIMEOUT_MS` | 5000 | Request timeout for remote hosts | | `WORKSPACE_MCP_OAUTH_PROXY_VALKEY_CONNECTION_TIMEOUT_MS` | 10000 | Connection timeout for remote hosts | **Encryption:** Disk and Valkey storage are encrypted with Fernet. The encryption key is derived from `FASTMCP_SERVER_AUTH_GOOGLE_JWT_SIGNING_KEY` if set, otherwise from `GOOGLE_OAUTH_CLIENT_SECRET`.
### External OAuth 2.1 Provider Mode The server supports an external OAuth 2.1 provider mode for scenarios where authentication is handled by an external system. In this mode, the MCP server does not manage the OAuth flow itself but expects valid bearer tokens in the Authorization header of tool calls. **Enabling External OAuth 2.1 Provider Mode:** ```bash # External OAuth provider mode requires OAuth 2.1 to be enabled export MCP_ENABLE_OAUTH21=true export EXTERNAL_OAUTH21_PROVIDER=true uv run main.py --transport streamable-http ``` **How It Works:** - **Protocol-level auth enabled**: All MCP requests (including `initialize` and `tools/list`) require a valid Bearer token, following the standard OAuth 2.1 flow. Unauthenticated requests receive a `401` with resource metadata pointing to Google's authorization server. - **External OAuth flow**: Your external system handles the OAuth flow and obtains Google access tokens (`ya29.*`) - **Token validation**: Server validates bearer tokens by calling Google's userinfo API - **Multi-user support**: Each request is authenticated independently based on its bearer token - **Resource metadata discovery**: The server serves `/.well-known/oauth-protected-resource` (RFC 9728) advertising Google as the authorization server and the required scopes **Key Features:** - **No local OAuth flow**: Server does not provide `/authorize`, `/token`, or `/register` endpoints β€” only resource metadata - **Bearer token only**: All authentication via `Authorization: Bearer ` headers - **Stateless by design**: Works seamlessly with `WORKSPACE_MCP_STATELESS_MODE=true` - **External identity providers**: Integrate with your existing authentication infrastructure **Requirements:** - Must be used with `MCP_ENABLE_OAUTH21=true` - OAuth credentials still required for token validation (`GOOGLE_OAUTH_CLIENT_ID`, `GOOGLE_OAUTH_CLIENT_SECRET`) - External system must obtain valid Google OAuth access tokens (ya29.*) - Each tool call request must include valid bearer token **Use Cases:** - Integrating with existing authentication systems - Custom OAuth flows managed by your application - API gateways that handle authentication upstream - Multi-tenant SaaS applications with centralized auth - Mobile or web apps with their own OAuth implementation ### Service Account Mode (Domain-Wide Delegation) > **WARNING: This mode uses Google Workspace domain-wide delegation, which grants the service account the ability to impersonate any user in your domain for the configured scopes. This is powerful and dangerous β€” do not use this unless you fully understand the security implications. A misconfigured service account with broad scopes can read, modify, and delete data across every user in your organization. Only use this in tightly controlled environments where you know exactly what you're doing.** Service account mode allows the server to authenticate using a Google Cloud service account with domain-wide delegation instead of interactive OAuth flows. The service account impersonates a single configured domain user for all API calls. **When to use service account mode:** - Headless or unattended environments where no browser is available for OAuth consent - Server-to-server integrations that need to act on behalf of a specific domain user - CI/CD pipelines or automation scripts - Environments where you cannot or do not want to manage per-user OAuth tokens **Enabling Service Account Mode:** ```bash # Option 1: Key file on disk export GOOGLE_SERVICE_ACCOUNT_KEY_FILE="/path/to/service-account-key.json" export USER_GOOGLE_EMAIL="user@yourdomain.com" uv run main.py # Option 2: Inline JSON key (e.g., from a secret manager) export GOOGLE_SERVICE_ACCOUNT_KEY_JSON='{"type":"service_account","project_id":"...","private_key":"...","client_email":"..."}' export USER_GOOGLE_EMAIL="user@yourdomain.com" uv run main.py ``` **Prerequisites:** 1. A Google Cloud service account with a JSON key 2. Domain-wide delegation enabled for the service account in your Google Workspace Admin Console (Security β†’ API controls β†’ Domain-wide delegation) 3. The required OAuth scopes authorized for the service account's client ID in the Admin Console 4. `USER_GOOGLE_EMAIL` set to the domain user the service account will impersonate **Incompatibilities:** - Cannot be combined with `--single-user` mode - Cannot be combined with `MCP_ENABLE_OAUTH21=true` - Only one key source may be provided β€” set either `GOOGLE_SERVICE_ACCOUNT_KEY_FILE` or `GOOGLE_SERVICE_ACCOUNT_KEY_JSON`, not both **Key Behaviors:** - The OAuth callback server is not started (no interactive auth needed) - Credentials directory permission checks are skipped - **All operations impersonate the configured `USER_GOOGLE_EMAIL`** β€” any email addresses supplied in tool calls (e.g., `user_email` parameters) are ignored. This differs from OAuth modes where each user authenticates separately. - The service account key is validated at startup (checks for required fields and correct type) ### VS Code MCP Client Support > **βœ… Recommended**: VS Code MCP extension properly supports the full MCP specification. **Always use HTTP transport mode** for proper OAuth 2.1 authentication.
πŸ†š VS Code Configuration ← Setup for VS Code MCP extension ```json { "servers": { "google-workspace": { "url": "http://localhost:8000/mcp/", "type": "http" } } } ``` *Note: Make sure to start the server with `--transport streamable-http` when using VS Code MCP.*
### Claude Code MCP Client Support > **βœ… Recommended**: Claude Code is a modern MCP client that properly supports the full MCP specification. **Always use HTTP transport mode** with Claude Code for proper OAuth 2.1 authentication and multi-user support.
πŸ†š Claude Code Configuration ← Setup for Claude Code MCP support ```bash # Start the server in HTTP mode first uv run main.py --transport streamable-http # Then add to Claude Code claude mcp add --transport http workspace-mcp http://localhost:8000/mcp ```
#### Reverse Proxy Setup If you're running the MCP server behind a reverse proxy (nginx, Apache, Cloudflare, etc.), you have two configuration options: **Problem**: When behind a reverse proxy, the server constructs OAuth URLs using internal ports (e.g., `http://localhost:8000`) but external clients need the public URL (e.g., `https://your-domain.com`). **Solution 1**: Set `WORKSPACE_EXTERNAL_URL` for all OAuth endpoints: ```bash # This configures all OAuth endpoints to use your external URL export WORKSPACE_EXTERNAL_URL="https://your-domain.com" ``` **Solution 2**: Set `GOOGLE_OAUTH_REDIRECT_URI` for just the callback: ```bash # This only overrides the OAuth callback URL export GOOGLE_OAUTH_REDIRECT_URI="https://your-domain.com/oauth2callback" ``` You also have options for: | `OAUTH_CUSTOM_REDIRECT_URIS` *(optional)* | Comma-separated list of additional redirect URIs | | `OAUTH_ALLOWED_ORIGINS` *(optional)* | Comma-separated list of additional CORS origins | **Important**: - Use `WORKSPACE_EXTERNAL_URL` when all OAuth endpoints should use the external URL (recommended for reverse proxy setups) - Use `GOOGLE_OAUTH_REDIRECT_URI` when you only need to override the callback URL - The redirect URI must exactly match what's configured in your Google Cloud Console - Your reverse proxy must forward OAuth-related requests (`/oauth2callback`, `/oauth2/*`, `/.well-known/*`) to the MCP server
πŸš€ Advanced uvx Commands ← More startup options ```bash # Configure credentials first (see Credential Configuration section) # Start with specific tools only uvx workspace-mcp --tools gmail drive calendar tasks # Start with tool tiers (recommended for most users) uvx workspace-mcp --tool-tier core # Essential tools uvx workspace-mcp --tool-tier extended # Core + additional features uvx workspace-mcp --tool-tier complete # All tools # Start in HTTP mode for debugging uvx workspace-mcp --transport streamable-http ```
*Requires Python 3.10+ and [uvx](https://github.com/astral-sh/uv). The package is available on [PyPI](https://pypi.org/project/workspace-mcp).* ### Development Installation For development or customization: ```bash git clone https://github.com/taylorwilsdon/google_workspace_mcp.git cd google_workspace_mcp uv run main.py ``` **Development Installation (For Contributors)**:
πŸ”§ Developer Setup JSON ← For contributors & customization ```json { "mcpServers": { "google_workspace": { "command": "uv", "args": [ "run", "--directory", "/path/to/repo/google_workspace_mcp", "main.py" ], "env": { "GOOGLE_OAUTH_CLIENT_ID": "your-client-id", "GOOGLE_OAUTH_CLIENT_SECRET": "your-secret", "OAUTHLIB_INSECURE_TRANSPORT": "1" } } } } ```
#### HTTP Mode (For debugging or web interfaces) If you need to use HTTP mode with Claude Desktop: ```json { "mcpServers": { "google_workspace": { "command": "npx", "args": ["mcp-remote", "http://localhost:8000/mcp"] } } } ``` *Note: Make sure to start the server with `--transport streamable-http` when using HTTP mode.* ### First-Time Authentication The server uses **Google Desktop OAuth** for simplified authentication: - **No redirect URIs needed**: Desktop OAuth clients handle authentication without complex callback URLs - **Automatic flow**: The server manages the entire OAuth process transparently - **Transport-agnostic**: Works seamlessly in both stdio and HTTP modes When calling a tool: 1. Server returns authorization URL 2. Open URL in browser and authorize 3. Google provides an authorization code 4. Paste the code when prompted (or it's handled automatically) 5. Server completes authentication and retries your request --- ## β—† Development ### Project Structure ``` google_workspace_mcp/ β”œβ”€β”€ auth/ # Authentication system with decorators β”œβ”€β”€ core/ # MCP server and utilities β”œβ”€β”€ g{service}/ # Service-specific tools β”œβ”€β”€ main.py # Server entry point β”œβ”€β”€ client_secret.json # OAuth credentials (not committed) └── pyproject.toml # Dependencies ``` ### Adding New Tools ```python from auth.service_decorator import require_google_service @require_google_service("drive", "drive_read") # Service + scope group async def your_new_tool(service, param1: str, param2: int = 10): """Tool description""" # service is automatically injected and cached result = service.files().list().execute() return result # Return native Python objects ``` ### Architecture Highlights - **Service Caching**: 30-minute TTL reduces authentication overhead - **Scope Management**: Centralized in `SCOPE_GROUPS` for easy maintenance - **Error Handling**: Native exceptions instead of manual error construction - **Multi-Service Support**: `@require_multiple_services()` for complex tools ### Credential Store System The server includes an abstract credential store API and a default backend for managing Google OAuth credentials with support for multiple storage backends: **Features:** - **Abstract Interface**: `CredentialStore` base class defines standard operations (get, store, delete, list users) - **Local File Storage**: `LocalDirectoryCredentialStore` implementation stores credentials as JSON files - **Configurable Storage**: Environment variable `GOOGLE_MCP_CREDENTIALS_DIR` sets storage location - **Multi-User Support**: Store and manage credentials for multiple Google accounts - **Automatic Directory Creation**: Storage directory is created automatically if it doesn't exist **Configuration:** ```bash # Optional: Set custom credentials directory export GOOGLE_MCP_CREDENTIALS_DIR="/path/to/credentials" # Default locations (if GOOGLE_MCP_CREDENTIALS_DIR not set): # - ~/.google_workspace_mcp/credentials (if home directory accessible) # - ./.credentials (fallback) ``` **Usage Example:** ```python from auth.credential_store import get_credential_store # Get the global credential store instance store = get_credential_store() # Store credentials for a user store.store_credential("user@example.com", credentials) # Retrieve credentials creds = store.get_credential("user@example.com") # List all users with stored credentials users = store.list_users() ``` The credential store automatically handles credential serialization, expiry parsing, and provides error handling for storage operations. --- ## ⊠ Security - **Prompt Injection**: This MCP server has the capability to retrieve your email, calendar events and drive files. Those emails, events and files could potentially contain prompt injections - i.e. hidden white text that tells it to forward your emails to a different address. You should exercise caution and in general, only connect trusted data to an LLM! - **Credentials**: Never commit `.env`, `client_secret.json` or the `.credentials/` directory to source control! - **OAuth Callback**: Uses `http://localhost:8000/oauth2callback` for development (requires `OAUTHLIB_INSECURE_TRANSPORT=1`) - **Transport-Aware Callbacks**: Stdio mode starts a minimal HTTP server only for OAuth, ensuring callbacks work in all modes - **Production**: Use HTTPS & OAuth 2.1 and configure accordingly - **Scope Minimization**: Tools request only necessary permissions - **Local File Access Control**: Tools that read local files (e.g., attachments, `file://` uploads) are restricted to the user's home directory by default. Override this with the `ALLOWED_FILE_DIRS` environment variable: ```bash # Colon-separated list of directories (semicolon on Windows) from which local file reads are permitted export ALLOWED_FILE_DIRS="/home/user/documents:/data/shared" ``` Regardless of the allowlist, access to sensitive paths (`.env`, `.ssh/`, `.aws/`, `/etc/shadow`, credential files, etc.) is always blocked. --- --- ## ≑ License MIT License - see `LICENSE` file for details. --- Validations: [![MCP Badge](https://lobehub.com/badge/mcp/taylorwilsdon-google_workspace_mcp)](https://lobehub.com/mcp/taylorwilsdon-google_workspace_mcp) [![Verified on MseeP](https://mseep.ai/badge.svg)](https://mseep.ai/app/eebbc4a6-0f8c-41b2-ace8-038e5516dba0)
Batch Emails