mcp-gee-sweet

Pre-release

This release is a pre-release and may not be stable for production use.

mcp-gee-sweet

Your AI Assistant's Gateway to Google Workspace!

GitHub License

An MCP server that gives AI clients reliable, direct access to Google Workspace — Sheets, Drive, Docs (HTML or Markdown content), and Calendar. 101 tools across four domains.

As of mid-2026, Google's own Workspace MCP servers (Developer Preview) cover Gmail, Drive, Calendar, People, and Chat — Sheets and Docs still have no official server at all, and Drive/Calendar coverage there is a fraction of what's here. Stable releases ship to PyPI behind a QA regression gate, with a raw batch_update passthrough as an escape hatch for anything a named tool doesn't cover yet. See Why it exists for the full, sourced comparison against both the official servers and community alternatives.

Install (stable):

uvx mcp-gee-sweet

Install (bleeding edge — every code change on develop):

uvx --prerelease=allow mcp-gee-sweet

Full documentation →

Quick start

Option A: `uv` — local use and development

If you cloned the repo or just want to use the server from your machine, uv is all you need. No Docker required.

git clone https://github.com/khuisman/mcp-gee-sweet.git
cd mcp-gee-sweet
uv sync

Then point your MCP client at it using stdio transport (see MCP client config below). The client spawns the server as a subprocess on demand — each session gets its own isolated process, so restarting the server for a code change or config update doesn't affect other open sessions.

Option B: Docker — persistent shared server (SSE)

Use Docker when you want a single long-running server that multiple clients connect to over SSE — for example, Claude Desktop talking to the same instance as Claude Code.

git clone https://github.com/khuisman/mcp-gee-sweet.git
cd mcp-gee-sweet
make build   # build the container image
make start   # start the server (SSE on port 47000)
make logs    # tail logs

Point your MCP client at http://localhost:47000/sse.

Note: when using SSE, all clients share one server process. After a code change or restart (make restart), you must also restart each MCP client to reconnect.

Configuration

The server tries auth methods in a waterfall by default, OAuth first — it authenticates as you and has full personal Drive access, which is what local/dev use (Option A above) needs. For OAuth, download an OAuth Client ID JSON from GCP Console and point the server at it:

export CREDENTIALS_PATH="/path/to/credentials.json"

Service accounts (recommended for headless server deployments — see Option B above), base64 credential injection, and Application Default Credentials are also supported. See Authentication for all options.

MCP client config

Claude Desktop — stdio (cloned repo):

{
  "mcpServers": {
    "mcp-gee-sweet": {
      "command": "uv",
      "args": ["run", "--directory", "/path/to/mcp-gee-sweet", "mcp-gee-sweet"],
      "env": {
        "CREDENTIALS_PATH": "/path/to/credentials.json"
      }
    }
  }
}

Claude Desktop — SSE (Docker):

{
  "mcpServers": {
    "mcp-gee-sweet": {
      "transport": "sse",
      "url": "http://localhost:47000/sse"
    }
  }
}

See Client Setup for more options including tool filtering.

Docs

Tools — full tool reference (101 tools)
Authentication — all four auth methods
Configuration — env vars, caching, tool filtering
Client Setup — MCP client config examples
Design Principles — tool inclusion policy, composite tool decisions
Roadmap — planned features and known gaps

Contributing

See CONTRIBUTING.md for setup, QA workflows, and PR guidelines. A signed-off docs/qa/runs/vX.Y.Z.md record is required before any stable PyPI release — see docs/qa/README.md for the QA workflow.

License

MIT — see LICENSE.

Credits

xing5/mcp-google-sheets — upstream this project was forked from
FastMCP
freema/mcp-gsheets and piotr-agier/google-drive-mcp — roadmap inspiration

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

mcp_gee_sweet-0.8.2.dev264.tar.gz (800.0 kB view details)

Uploaded Aug 8, 2026 Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

The dropdown lists show the available interpreters, ABIs, and platforms. Enable javascript to be able to filter the list of wheel files.

mcp_gee_sweet-0.8.2.dev264-py3-none-any.whl (167.4 kB view details)

Uploaded Aug 8, 2026 Python 3

File details

Details for the file mcp_gee_sweet-0.8.2.dev264.tar.gz.

File metadata

Download URL: mcp_gee_sweet-0.8.2.dev264.tar.gz
Upload date: Aug 8, 2026
Size: 800.0 kB
Tags: Source
Uploaded using Trusted Publishing? Yes
Uploaded via: twine/7.0.0 CPython/3.13.14

File hashes

Hashes for mcp_gee_sweet-0.8.2.dev264.tar.gz
Algorithm	Hash digest
SHA256	`d66f30ec598ab78fe69a635f74394d6c41532ed8aa620b736ba71a014c7200cb`
MD5	`af05747597264ce1d5ac534286c04eee`
BLAKE2b-256	`07db188a914a852ea98379a172312245b73139eefa38f043852a6b262184269f`

See more details on using hashes here.

Provenance

The following attestation bundles were made for mcp_gee_sweet-0.8.2.dev264.tar.gz:

Publisher: publish-dev.yml on khuisman/mcp-gee-sweet

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Statement:
- Statement type: https://in-toto.io/Statement/v1
- Predicate type: https://docs.pypi.org/attestations/publish/v1
- Subject name: mcp_gee_sweet-0.8.2.dev264.tar.gz
- Subject digest: d66f30ec598ab78fe69a635f74394d6c41532ed8aa620b736ba71a014c7200cb
- Sigstore transparency entry: 2377791944
- Sigstore integration time: Aug 8, 2026
Source repository:
- Permalink: khuisman/mcp-gee-sweet@39539ddf72bb97eac3d0d8ecd59e416c52c03064
- Branch / Tag: refs/heads/develop
- Owner: https://github.com/khuisman
- Access: public
Publication detail:
- Token Issuer: https://token.actions.githubusercontent.com
- Runner Environment: github-hosted
- Publication workflow: publish-dev.yml@39539ddf72bb97eac3d0d8ecd59e416c52c03064
- Trigger Event: push