Skip to content

mcp-gee-sweet

An MCP server that gives AI clients deep, direct access to Google Workspace — Sheets, Drive, Docs, Calendar, and Gmail.

What it does

  • Read and write Google Sheets — cell values, formulas, sheet structure, batch updates
  • Manage Google Drive — list, search, upload, download, move, copy, and sync files and folders
  • Work with Google Docs — create documents, read content, write formatted content from HTML or Markdown
  • Access Google Calendar — list calendars and events, create and update events, find free slots
  • Use Gmail — search and read messages and threads, send and reply, manage drafts and labels (OAuth only)

Why it exists

This project started as a fork of xing5/mcp-google-sheets and has since diverged substantially — full Sheets read/write/formulas/structure/formatting/charts plus a raw batch_update passthrough for anything a named tool doesn't cover, an AST-based Docs pipeline (HTML and Markdown input, theming, structural table editing), Drive file/sharing/sync operations, Calendar, and Gmail. See Project Fork for the original fork history.

This project deliberately consolidates related operations into fewer, more parameterized tools, with batch_update as the escape hatch for whatever doesn't fit a named tool — see Design Principles for the reasoning ("Tool count as a cost").

Known gaps (full comments CRUD, conditional formatting, protected ranges, multi-tab Docs, and more) are tracked as candidates in the roadmap, not silently ignored.

Key design decisions

Tool count is a cost. Every registered tool is a name the AI must reason about on every call. This server applies a strict inclusion test — see Design Principles — and defers borderline cases to the batch_update passthrough rather than adding named tools speculatively.

Composite tools only when it matters. Multi-step workflows are left to the AI client unless they involve binary data, pagination loops, or encoding decisions that Claude handles inconsistently in practice. See Design Principles for the policy.

Caching by default. Sheet structure, sheet data, Drive folder listings, doc content, and calendar metadata are all cached in a local SQLite database with TTL + dirty invalidation. See Configuration for details.

Quickstart

# Run locally
uv run mcp-gee-sweet

# Docker
docker run --rm -p 127.0.0.1:8000:8000 \
  -e MCP_SERVER_TOKEN=<token> \
  -e CREDENTIALS_CONFIG=<base64-service-account> \
  -e DRIVE_FOLDER_ID=<folder-id> \
  mcp-gee-sweet

Reference