This release is a pre-release and may not be stable for production use.
mcp-gee-sweet
The Google Workspace MCP server built for depth.
Google ships its own Sheets and Docs MCP servers now (Developer Preview), but they're shallow — thin CRUD, both approval-gated. mcp-gee-sweet goes deeper: raw formula access — reads =VLOOKUP() and friends directly, structural Docs support (colspan/rowspan tables, themes, named styles, an HTML/Markdown→AST→Docs pipeline), plus complete Drive and Calendar coverage Google's preview doesn't touch at all.
A few things no other Workspace MCP has:
- Caching — repeated reads return in ~2ms from a local cache instead of a round-trip API call every time.
- Formula access — reads raw
=VLOOKUP(),=SUM(), and=IF()expressions, not just the values they produce. - Local sync — two-way sync between a local folder and Google Drive.
Install (stable):
uvx mcp-gee-sweet
Install (bleeding edge — every code change on develop):
uvx --prerelease=allow mcp-gee-sweet
What's covered
| Service | Tools | Google's own MCP | Highlights |
|---|---|---|---|
| Google Sheets | 35 | 6 | Formula access, batch read/write, 8 chart types, structural ops |
| Google Drive | 38 | — | File ops, sharing/permissions, local sync, revision history |
| Google Docs | 34 | 2 | Full HTML→Doc pipeline, tables, range styling, themes, Markdown export |
| Google Calendar | 17 | — | Event CRUD, free-slot finder across multiple calendars |
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, grouped by domain
- 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
1 maintainer
Release files for mcp-gee-sweet 0.9.1.dev103
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mcp_gee_sweet-0.9.1.dev103.tar.gz | 2.6 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_gee_sweet-0.9.1.dev103-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.9 MB
Release files / mcp_gee_sweet-0.9.1.dev103.tar.gz
| Download URL | mcp_gee_sweet-0.9.1.dev103.tar.gz |
|---|---|
| Size | 2.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
95b77982df4c19b3254c830aba644047541ee7723b3f3fc8dc045d6026ab154a
|
|
BLAKE2b-256 checksum How to use checksums |
121aaf176b5606ff3c28ed1914f71a7c068e1c247c6031078fec35a5097607c1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 21, 2026.
Transparency logRelease files / mcp_gee_sweet-0.9.1.dev103-py3-none-any.whl
| Download URL | mcp_gee_sweet-0.9.1.dev103-py3-none-any.whl |
|---|---|
| Size | 223.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3c77f77295ae4a25eb63b0a026068ae207e5ae2a66e4f1185387768674d39496
|
|
BLAKE2b-256 checksum How to use checksums |
6aba0d13c895364d2a315adafd0584988748fb6abf9ed86ed439340f5ce45db6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 21, 2026.
Transparency log
