What it does
Workspace Operator is a local MCP server that gives AI agents 132 tools across Google Drive, Docs, Sheets, Slides, Gmail, Calendar, Apps Script, Tasks, Forms and Postmaster. It covers cross-service search, file upload and export, sheet formatting, slide assembly, threaded Gmail replies and attachments. Writes are staged, bulk operations follow a plan, confirm, run and undo sequence, and tool annotations flag destructive actions. Server-side tool profiles (read-only, read-write, full) control which tools are exposed.
It suits cases where an agent should change a workspace and those changes can be rolled back, such as moving a message to Trash, formatting a spreadsheet, building a deck from a table, or staging Apps Script updates with backups. The publisher notes that official Google servers are a better fit for simply asking questions about mail. The server is designed for one user and one Google account per instance, not for shared or multi-tenant use.
It runs on your own machine and connects to Google through your own OAuth client. For a single desktop client it runs as a stdio child process; for several clients it runs in Docker over HTTP with a bearer token. Setup requires a Google Cloud project with the relevant APIs enabled, a configured OAuth consent screen, a Desktop app OAuth client, and a one-time authorization. The source install requires Python.
Limitations and requirements
Requires a Google Cloud project, enabled Google APIs and a Desktop app OAuth client, plus a one-time browser sign-in. While the consent screen is in Testing, the account must be added as a test user. Designed for a single user and one Google account per instance; any holder of a valid bearer token can call every exposed tool and cancel bulk jobs in that instance, and there is no per-user authentication or data separation. Not intended for public or multi-tenant services. Source install requires Python. Postmaster Tools is optional and useful only for verified domains.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 16 Nov 2026 · its page on the source
Workspace Operator
Google Workspace automation for AI agents: 39 tools, human-approved deletes, bulk undo.
v2.1.2As shown on registry.modelcontextprotocol.io when we last read it