What is Google Workspace Mcp

google_workspace_mcp is a Model Context Protocol (MCP) server designed to integrate Google Workspace services, such as Google Calendar, with AI assistants and other applications. It acts as a bridge for secure interaction with Google Workspace data via Google’s APIs.

Use cases

Use cases include building AI assistants that manage Google Calendar events, creating applications that integrate Google Workspace functionalities, and developing tools for automated scheduling and event management.

How to use

To use google_workspace_mcp, clone the repository from GitHub, install the required dependencies using the ‘uv’ package installer, and set up a Google Cloud Project with the necessary APIs and OAuth 2.0 credentials configured.

Key features

Key features include OAuth 2.0 Authentication for secure API access, Google Calendar Integration for listing calendars and fetching events, compliance with MCP standards, support for both Stdio and HTTP transport, and extensibility for adding more Google Workspace API support.

Where to use

google_workspace_mcp can be used in various fields such as software development, AI integration, and any application requiring interaction with Google Workspace services.

---

See it in action:

---

🌐 Overview

A production-ready MCP server that integrates all major Google Workspace services with AI assistants. Built with FastMCP for optimal performance, featuring advanced authentication handling, service caching, and streamlined development patterns.

✨ Features

• 🔐 Advanced OAuth 2.0: Secure authentication with automatic token refresh, transport-aware callback handling, session management, and centralized scope management
• 📅 Google Calendar: Full calendar management with event CRUD operations
• 📁 Google Drive: File operations with native Microsoft Office format support (.docx, .xlsx)
• 📧 Gmail: Complete email management with search, send, and draft capabilities
• 📄 Google Docs: Document operations including content extraction and creation
• 📊 Google Sheets: Comprehensive spreadsheet management with flexible cell operations
• 🖼️ Google Slides: Presentation management with slide creation, updates, and content manipulation
• 📝 Google Forms: Form creation, retrieval, publish settings, and response management
• 💬 Google Chat: Space management and messaging capabilities
• 🔄 Multiple Transports: HTTP with SSE fallback, OpenAPI compatibility via mcpo
• ⚡ High Performance: Service caching, thread-safe sessions, FastMCP integration
• 🧩 Developer Friendly: Minimal boilerplate, automatic service injection, centralized configuration

---

🚀 Quick Start

Simplest Start (uvx - Recommended)

Run instantly without manual installation - you must set the GOOGLE_CLIENT_SECRETS environment variable with the path to your client_secret.json when using uvx as you won’t have a repo directory to pull from.

# Start the server with all Google Workspace tools
uvx workspace-mcp

# Start with specific tools only
uvx workspace-mcp --tools gmail drive calendar

# Start in HTTP mode for debugging
uvx workspace-mcp --transport streamable-http

Requires Python 3.11+ and uvx. The package is available on PyPI.

Development Installation

For development or customization:

git clone https://github.com/taylorwilsdon/google_workspace_mcp.git
cd google_workspace_mcp
uv run main.py

Prerequisites

• Python 3.11+
• uvx (for instant installation) or uv (for development)
• Google Cloud Project with OAuth 2.0 credentials

Configuration

1. Google Cloud Setup:

   • Create OAuth 2.0 credentials (web application) in Google Cloud Console
   • Enable APIs: Calendar, Drive, Gmail, Docs, Sheets, Slides, Forms, Chat
   • Download credentials as client_secret.json in project root
     • To use a different location for client_secret.json, you can set the GOOGLE_CLIENT_SECRETS environment variable with that path
   • Add redirect URI: http://localhost:8000/oauth2callback

2. Environment:

   export OAUTHLIB_INSECURE_TRANSPORT=1  # Development only
   

3. Server Configuration:
   The server’s base URL and port can be customized using environment variables:

   • WORKSPACE_MCP_BASE_URI: Sets the base URI for the server (default: http://localhost). This affects the server_url used for Gemini native function calling and the OAUTH_REDIRECT_URI.
   • WORKSPACE_MCP_PORT: Sets the port the server listens on (default: 8000). This affects the server_url, port, and OAUTH_REDIRECT_URI.

Start the Server

# Default (stdio mode for MCP clients)
uv run main.py

# HTTP mode (for web interfaces and debugging)
uv run main.py --transport streamable-http

# Single-user mode (simplified authentication)
uv run main.py --single-user

# Selective tool registration (only register specific tools)
uv run main.py --tools gmail drive calendar
uv run main.py --tools sheets docs
uv run main.py --single-user --tools gmail  # Can combine with other flags

# Docker
docker build -t workspace-mcp .
docker run -p 8000:8000 -v $(pwd):/app workspace-mcp --transport streamable-http

Available Tools for --tools flag: gmail, drive, calendar, docs, sheets, forms, chat

Connect to Claude Desktop

The server supports two transport modes:

Stdio Mode (Default - Recommended for Claude Desktop)

Option 1: Auto-install (Recommended)

python install_claude.py

Option 2: Manual Configuration

1. Open Claude Desktop Settings → Developer → Edit Config
2. This creates/opens the config file at:
   • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
   • Windows: %APPDATA%\Claude\claude_desktop_config.json
3. Add the server configuration:

{
  "mcpServers": {
    "google_workspace": {
      "command": "uvx",
      "args": [
        "workspace-mcp"
      ]
    }
  }
}

Alternative (Development Installation):

{
  "mcpServers": {
    "google_workspace": {
      "command": "uv",
      "args": [
        "run",
        "main.py"
      ],
      "cwd": "/path/to/google_workspace_mcp"
    }
  }
}

HTTP Mode (For debugging or web interfaces)

If you need to use HTTP mode with Claude Desktop:

{
  "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 features transport-aware OAuth callback handling:

• Stdio Mode: Automatically starts a minimal HTTP server on port 8000 for OAuth callbacks
• HTTP Mode: Uses the existing FastAPI server for OAuth callbacks
• Same OAuth Flow: Both modes use http://localhost:8000/oauth2callback for consistency

When calling a tool:

1. Server returns authorization URL
2. Open URL in browser and authorize
3. Server handles OAuth callback automatically (on port 8000 in both modes)
4. Retry the original request

---

🧰 Available Tools

Note: All tools support automatic authentication via @require_google_service() decorators with 30-minute service caching.

📅 Google Calendar (calendar_tools.py)

Tool	Description
list_calendars	List accessible calendars
get_events	Retrieve events with time range filtering
get_event	Fetch detailed information of a single event by ID
create_event	Create events (all-day or timed) with optional Drive file attachments
modify_event	Update existing events
delete_event	Remove events

📁 Google Drive (drive_tools.py)

Tool	Description
search_drive_files	Search files with query syntax
get_drive_file_content	Read file content (supports Office formats)
list_drive_items	List folder contents
create_drive_file	Create new files or fetch content from public URLs

📧 Gmail (gmail_tools.py)

Tool	Description
search_gmail_messages	Search with Gmail operators
get_gmail_message_content	Retrieve message content
send_gmail_message	Send emails
draft_gmail_message	Create drafts

📝 Google Docs (docs_tools.py)

Tool	Description
search_docs	Find documents by name
get_doc_content	Extract document text
list_docs_in_folder	List docs in folder
create_doc	Create new documents

📊 Google Sheets (sheets_tools.py)

Tool	Description
list_spreadsheets	List accessible spreadsheets
get_spreadsheet_info	Get spreadsheet metadata
read_sheet_values	Read cell ranges
modify_sheet_values	Write/update/clear cells
create_spreadsheet	Create new spreadsheets
create_sheet	Add sheets to existing files

📝 Google Forms (forms_tools.py)

Tool	Description
create_form	Create new forms with title and description
get_form	Retrieve form details, questions, and URLs
set_publish_settings	Configure form template and authentication settings
get_form_response	Get individual form response details
list_form_responses	List all responses to a form with pagination

💬 Google Chat (chat_tools.py)

Tool	Description
list_spaces	List chat spaces/rooms
get_messages	Retrieve space messages
send_message	Send messages to spaces
search_messages	Search across chat history

---

🛠️ 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

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

---

🔒 Security

• Credentials: Never commit client_secret.json or .credentials/ directory
• 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 for callback URIs and configure accordingly
• Network Exposure: Consider authentication when using mcpo over networks
• Scope Minimization: Tools request only necessary permissions

---

🌐 Integration with Open WebUI

To use this server as a tool provider within Open WebUI:

1. Create MCPO Configuration

Create a file named config.json with the following structure to have mcpo make the streamable HTTP endpoint available as an OpenAPI spec tool:

{
  "mcpServers": {
    "google_workspace": {
      "type": "streamablehttp",
      "url": "http://localhost:8000/mcp"
    }
  }
}

2. Start the MCPO Server

mcpo --port 8001 --config config.json --api-key "your-optional-secret-key"

This command starts the mcpo proxy, serving your active (assuming port 8000) Google Workspace MCP on port 8001.

3. Configure Open WebUI

1. Navigate to your Open WebUI settings
2. Go to “Connections” → “Tools”
3. Click “Add Tool”
4. Enter the Server URL: http://localhost:8001/google_workspace (matching the mcpo base URL and server name from config.json)
5. If you used an --api-key with mcpo, enter it as the API Key
6. Save the configuration

The Google Workspace tools should now be available when interacting with models in Open WebUI.

---

📄 License

MIT License - see LICENSE file for details.

---