aaronsb/google-workspace-mcp
A Model Context Protocol (MCP) server that provides authenticated access to Google Workspace APIs, offering integrated Authentication, Gmail, Calendar, and Drive functionality
What's novel
A Model Context Protocol (MCP) server that provides authenticated access to Google Workspace APIs, offering integrated Authentication, Gmail, Calendar, and Drive functionality
Code Analysis
10 files read · 3 roundsAn MCP server that gives AI agents typed, descriptor-driven access to Google Workspace APIs (Gmail, Calendar, Drive, Docs, Sheets, Tasks, Meet, Contacts) with a YAML-manifest code-generation factory, composable safety policies, a scratchpad compose-edit-deliver workflow, and multi-account OAuth orch
Strengths
Exceptional architectural discipline: the descriptor-driven client makes invalid API calls compile errors, the factory+patch system cleanly separates declarative service definitions from domain-specific logic, and the safety policy layer enforces per-account consent with thoughtful fail-open semantics. The codebase is deeply documented with ADR references, and every design decision (retry with jitter, bounded hydration concurrency, streamed downloads, resumable uploads) is justified by a concret
Weaknesses
The factory system, while elegant, adds an indirection layer that makes tracing a specific operation's full execution path (manifest → generator → patch → client) require reading multiple files. The scratchpad and queue systems, while well-designed, are complex enough that their interaction with the factory-generated handlers creates subtle coupling (e.g., scratchpad must explicitly call safety policies that factory tools get for free).
Score Breakdown
Signal breakdown
Innovation
Craft
Traction
Scope
Evidence
Commits
24
Contributors
4
Files
66
Active weeks
6
Repository
Language
TypeScript
Stars
125
Forks
36
License
MIT