Google Workspace MCP server for Sheets, Docs, Drive, Calendar, and Gmail, built for depth.
概览
mcp-gee-sweet A Google Workspace MCP server built for depth. mcp-gee-sweet gives AI clients deep, direct access to Google Sheets, Docs, Drive, Calendar, and Gmail. It reads raw formulas like =VLOOKUP(), builds Docs structurally (colspan/rowspan tables, themes, named styles, an HTML/Markdown→AST→Docs pipeline), and covers Drive files, sharing, and sync alongside Calendar events and Gmail messages, threads, and drafts. A few highlights: - — repeated reads return in ~2ms from a local cache instead of a round-trip API call every time. - — reads raw =VLOOKUP(), =SUM(), and =IF() expressions, not just the values they produce. - — two-way sync between a local folder and Google Drive. If you cloned the repo or just want to use the server from your machine, uv is all you need. No Docker required. Then point your MCP client at it using (see MCP client config below).
README
以下为原文 README 节选，完整内容请查看原文。
mcp-gee-sweet gives AI clients deep, direct access to Google Sheets, Docs, Drive, Calendar, and Gmail. It reads raw formulas like =VLOOKUP(), builds Docs structurally (colspan/rowspan tables, themes, named styles, an HTML/Markdown→AST→Docs pipeline), and covers Drive files, sharing, and sync alongside Calendar events and Gmail messages, threads, and drafts.
A few highlights:
- 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 | Highlights |
|---|---|---|
| Google Sheets | 36 | Formula access, batch read/write, 8 chart types, structural ops |
| Google Drive | 38 | File ops, sharing/permissions, local sync, revision history |
| Google Docs | 34 | Full HTML→Doc pipeline, tables, range styling, themes, Markdown export |
| Google Calendar | 17 | Event CRUD, free-slot finder across multiple calendars |
| Gmail | 15 | Search and read messages and threads, send and reply, drafts you can review, edit, or discard before sending, labels (OAuth only). By default nothing is sent until the user confirms it; a client that can’t ask leaves the email as a draft. See Gmail sending |
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安装
uvx mcp-gee-sweet配置
{
"mcpServers": {
"mcp-gee-sweet": {
"command": "uv",
"args": ["run", "--directory", "/path/to/mcp-gee-sweet", "mcp-gee-sweet"],
"env": {
"CREDENTIALS_PATH": "/path/to/credentials.json",
"TOKEN_PATH": "/path/to/token.json"
}
}
}
}