gworkspace-mcp

gworkspace-mcp

A production-ready MCP server that gives AI assistants full, authenticated access to the entire Google Workspace ecosystem.

Category
Visit Server

README

šŸš€ gworkspace-mcp

A production-ready Model Context Protocol (MCP) server that gives AI assistants full, authenticated access to the entire Google Workspace ecosystem.

Python FastMCP Google APIs PostgreSQL License


šŸ“– Overview

gworkspace-mcp is a Model Context Protocol (MCP) server built with Python that acts as a secure, structured bridge between AI assistants (such as Claude, Cursor, or any MCP-compatible client) and the full suite of Google Workspace services.

Instead of writing one-off Google API scripts, this server exposes all Google Workspace functionality as named, type-safe MCP tools — each with clear docstrings, parameter descriptions, and async support. AI agents can call these tools in natural conversation to read emails, manage Drive files, schedule calendar events, and more, all authenticated against a real Google account.

The server handles the entire OAuth 2.0 lifecycle automatically: first-time browser-based authorization, secure token persistence in PostgreSQL, and silent token refresh using stored refresh tokens — so users never need to re-authenticate.


✨ Features

Feature Description
šŸ“§ Gmail Search, read, send, label, delete emails and download attachments
šŸ“ Google Drive Search, upload, download, create folders, share, and delete files
šŸ“† Google Calendar Create, list, update, and delete events with attendees and reminders
āœ… Google Tasks Full task and tasklist management including subtasks
šŸ“ Google Docs Create, read, append, insert, replace, format text, and insert tables in documents
šŸ” OAuth 2.0 Automated first-time browser login with persistent token storage
šŸ”„ Token Refresh Automatic silent refresh of expired access tokens
šŸ—„ļø PostgreSQL Storage Per-user token persistence using SQLAlchemy ORM
⚔ Async Architecture All MCP tools are fully async for non-blocking execution

šŸ—ļø Architecture

The project follows a clean, layered architecture that separates concerns across four distinct layers:

gworkspace-mcp/
│
ā”œā”€ā”€ server.py               # Entry point — initializes FastMCP, registers all tools
ā”œā”€ā”€ main.py                 # Minimal demo entry point
ā”œā”€ā”€ pyproject.toml          # Project metadata and dependency declarations
│
ā”œā”€ā”€ auth/                   # Layer 1: Authentication
│   ā”œā”€ā”€ google_auth.py      # OAuth 2.0 flow (first-time login + credential retrieval)
│   └── token_manager.py    # CRUD operations on the token store (get/save/update/delete)
│
ā”œā”€ā”€ db/                     # Layer 2: Persistence
│   ā”œā”€ā”€ database.py         # SQLAlchemy engine, session factory, and Base class
│   └── models.py           # ORM model: Tokens table (email, access_token, refresh_token, expiry)
│
ā”œā”€ā”€ services/               # Layer 3: Business Logic
│   ā”œā”€ā”€ gmail_service.py    # Google Gmail API calls (search, read, send, label, delete)
│   ā”œā”€ā”€ drive_service.py    # Google Drive API calls (search, upload, download, share, delete)
│   ā”œā”€ā”€ calendar_service.py # Google Calendar API calls (create, list, update, delete)
│   ā”œā”€ā”€ tasks_service.py    # Google Tasks API calls (tasks, subtasks, tasklists)
│   ā”œā”€ā”€ docs_service.py     # Google Docs API calls (create, read, append, formatting)
│   └── sheets_service.py   # Google Sheets API calls (create, read, write, sheets, formatting)
│
ā”œā”€ā”€ tools/                  # Layer 4: MCP Tool Definitions
│   ā”œā”€ā”€ gmail.py            # 7 MCP tools wrapping gmail_service
│   ā”œā”€ā”€ drive.py            # 6 MCP tools wrapping drive_service
│   ā”œā”€ā”€ calendar.py         # 4 MCP tools wrapping calendar_service
│   ā”œā”€ā”€ tasks.py            # 8 MCP tools wrapping tasks_service
│   ā”œā”€ā”€ docs.py             # 8 MCP tools wrapping docs_service
│   └── sheets.py           # 10 MCP tools wrapping sheets_service
│
ā”œā”€ā”€ config/                 # Configuration (not committed to source control)
│   ā”œā”€ā”€ credentials.json    # Google OAuth client ID and secret
│   └── .env                # Environment variables (DATABASE_URL, etc.)
│
└── utils/
    └── helpers.py          # Shared utility functions

Data Flow

AI Client (Claude, Cursor, etc.)
        │
        │  MCP Protocol (stdio / SSE)
        ā–¼
   server.py  ──► FastMCP instance
        │
        ā–¼
   tools/*.py  ──► MCP tool definitions (@mcp.tool decorator)
        │
        ā–¼
   services/*.py  ──► Google API business logic
        │              (uses authenticated credentials)
        │
        ā”œā”€ā”€ā–ŗ auth/google_auth.py  ──► Retrieves or refreshes credentials
        │             │
        │             ā–¼
        │       auth/token_manager.py  ──► Reads/writes token from DB
        │                    │
        │                    ā–¼
        │             db/models.py + db/database.py  ──► PostgreSQL
        │
        ā–¼
   Google Workspace APIs (Gmail, Drive, Calendar, Tasks, ...)

šŸ” Authentication System

One of the most robust parts of this project is the multi-layer OAuth 2.0 authentication system.

How It Works

  1. First-time login: When a user's email is not found in the database, google_auth.py launches a local browser-based OAuth consent flow using InstalledAppFlow. After the user grants consent, the credentials are automatically saved to PostgreSQL.

  2. Subsequent calls: On every API call, get_google_credentials(email) looks up the stored token. If the access token is still valid, it is returned immediately. If expired, the refresh token is used to silently obtain a new access token via creds.refresh(Request()), and the updated token is persisted back to the database.

  3. Token Storage: Tokens are stored in a tokens table with the user's email as the primary key, along with access_token, refresh_token, scopes, and expiry — all managed through SQLAlchemy.

OAuth Scopes Requested

Scope Purpose
gmail.modify Read, send, search, and organize Gmail (without permanent deletion)
drive Full access to all Google Drive files
calendar.events View and edit all calendar events
tasks Create, update, and delete Google Tasks
spreadsheets Full access to Google Sheets
documents Full access to Google Docs

šŸ› ļø MCP Tools Reference

šŸ“§ Gmail Tools

Tool Description
search_the_gmails Search Gmail using any query string (e.g. is:unread, from:boss@company.com)
read_the_gmails Read full email content by message ID — returns body, sender, attachments
get_the_attachment Download a specific email attachment as base64 by attachment ID
create_the_gmail_label Create a new custom label for organizing emails
modify_the_gmail_labels Add or remove labels (including INBOX, SPAM, STARRED) from a message
delete_the_gmails Delete emails by trash, permanent, or batch strategy
send_the_gmails Compose and send an email with optional file attachment

šŸ“ Google Drive Tools

Tool Description
search_the_drive Search Drive files/folders by name, MIME type, or any Drive query
upload_to_the_drive Upload a single file or recursively upload an entire folder
create_the_folder Create a new Drive folder with optional parent folder
download_from_drive Download a Drive file to a local path
share_the_file Share a file with a user, group, domain, or make it public with role control
delete_the_drive_file Move a file to trash or permanently delete it

šŸ“† Google Calendar Tools

Tool Description
create_calender_events Create an event with title, time, location, guests, and reminders
list_calender_events List events within a date range, up to a configurable max
update_calender_event Update any field of an existing event
delete_calender_event Delete an event by its ID

āœ… Google Tasks Tools

Tool Description
create_the_tasklist Create a new named task list
create_the_task Create a task with title, notes, and due date
create_the_subtask Create a subtask nested under an existing parent task
update_the_task Update a task's title, notes, due date, or status (needsAction / completed)
list_the_tasks List tasks with filters (completed, hidden, due date, updated date)
list_the_tasklists List all task lists for the authenticated user
delete_the_task Permanently delete a task or subtask (cascades to subtasks)
delete_the_tasklists Permanently delete an entire task list and all its tasks

šŸ“ Google Docs Tools

Tool Description
create_the_document Create a new blank Google Document with a title
read_the_document Retrieve the full content and metadata of a Google Document by ID
append_the_document Append text at the end of a Google Document
insert_the_document_text Insert text at a specific character index in a Document
replace_the_document_text Find and replace all occurrences of a text string in a Document
delete_the_document_content Delete content between two character index positions
format_the_document_text Apply formatting (bold, italic, underline, font size, color) to text
insert_the_document_table Insert an empty table with specified rows and columns

šŸš€ Getting Started

Prerequisites

  • Python 3.12+
  • A PostgreSQL database instance
  • A Google Cloud Project with the following APIs enabled:
    • Gmail API
    • Google Drive API
    • Google Calendar API
    • Google Tasks API
    • Google Docs API
    • Google Sheets API
  • An OAuth 2.0 Client ID (Desktop app type) downloaded as credentials.json

Installation

# Clone the repository
git clone https://github.com/your-username/gworkspace-mcp.git
cd gworkspace-mcp

# Option 1: Using pip (editable install)
pip install -e .

# Option 2: Using uv (recommended)
uv sync

Configuration

1. Place your Google credentials:

config/credentials.json   ← your OAuth 2.0 client secret JSON from Google Cloud Console

2. Create the environment file:

# config/.env
DATABASE_URL=postgresql://user:password@localhost:5432/gworkspace_mcp

3. (First run only) A browser window will open asking you to authorize with your Google account. After authorization, tokens are stored in the database automatically.

Running the Server

python server.py

The MCP server will start and listen for connections from any MCP-compatible client.

Connecting to an MCP Client

To connect this server to Claude Desktop, add the following to your claude_desktop_config.json:

{
  "mcpServers": {
    "gworkspace": {
      "command": "python",
      "args": ["C:/path/to/gworkspace-mcp/server.py"]
    }
  }
}

🧩 Tech Stack

Technology Role
Python 3.12+ Core language
FastMCP 3.4+ MCP server framework — tool registration and protocol handling
Google API Python Client Official Google Workspace API client library
google-auth / google-auth-oauthlib OAuth 2.0 credential management and token refresh
SQLAlchemy 2.0 ORM for database models and session management
PostgreSQL Persistent storage for OAuth tokens
psycopg2-binary / asyncpg PostgreSQL drivers (sync + async)
python-dotenv Environment variable loading from .env file

šŸ“Œ Project Status

Component Status
Gmail (tools + service) āœ… Complete
Google Drive (tools + service) āœ… Complete
Google Calendar (tools + service) āœ… Complete
Google Tasks (tools + service) āœ… Complete
OAuth 2.0 + Token Management āœ… Complete
PostgreSQL Token Persistence āœ… Complete
Google Docs (tools + service) āœ… Complete
Google Sheets (tools + service) āœ… Complete
Automated Tests šŸ“‹ Planned
Docker Support šŸ“‹ Planned

šŸ›£ļø Roadmap

  • [x] Complete Google Docs service (create, read, update documents)
  • [x] Complete Google Sheets service (read, write, format, rows/columns manipulation)
  • [ ] Add comprehensive pytest test suite
  • [ ] Add Docker + Docker Compose setup for easy deployment
  • [ ] Add multi-user support with user session isolation
  • [ ] Add rate limiting and error retry logic
  • [ ] Publish to PyPI as an installable MCP server package

šŸ¤ Contributing

Contributions are welcome! Please open an issue first to discuss any significant changes. Make sure to:

  1. Follow the existing layered architecture (tools → services → auth/db)
  2. Add proper docstrings to all new MCP tool functions
  3. Test with a real Google account before submitting

āš ļø Security Notice

  • Never commit config/credentials.json or config/.env to version control.
  • Both files are listed in .gitignore by default.
  • OAuth tokens are stored in the database — ensure your PostgreSQL instance is secured appropriately.

šŸ“„ License

This project is licensed under the MIT License. See LICENSE for details.


<p align="center"> Built with ā¤ļø using <strong>FastMCP</strong> and the <strong>Google Workspace APIs</strong> </p>

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured