Google Workspace MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_SCOPES | No | OAuth 2.0 scopes required for project functionality | |
| GOOGLE_CLIENT_ID | Yes | Your Google Cloud OAuth 2.0 Client ID | |
| GOOGLE_REDIRECT_URI | Yes | Your OAuth 2.0 Redirect URI configured in Google Cloud | |
| GOOGLE_CLIENT_SECRET | Yes | Your Google Cloud OAuth 2.0 Client Secret |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| manage_accountsA | Manage Google Workspace account lifecycle: list, authenticate, check status, refresh credentials, update scopes, or remove accounts. |
| manage_workspaceB | Manage files and directories in the workspace sandbox. Supports nested paths (e.g. "reports/q1/summary.csv"). The workspace is the exchange point for file operations (attachments, downloads, exports). |
| manage_scratchpadA | Compose, edit, and deliver text content. Use for any multi-line content: emails, documents, descriptions. Compose in the scratchpad, edit by line or JSON path, attach files, then send to any target. For short one-liners, use the service tool directly instead. |
| bulk_operationsA | Do many things in one call, two ways. mode:'queue' (default) runs different operations in sequence, chaining results with $N.field — works for every tool. mode:'batch' does ONE operation across many resources in a single Google request — far fewer round trips, but only where Google publishes a batch method. |
| queue_operationsA | RENAMED to |
| manage_calendarB | List events, view agenda, check availability, or manage calendar events. |
| manage_contactsA | Search, read, create, update and delete Google Contacts: your saved contacts, the addresses you have corresponded with but never saved, and your organization's directory. |
| manage_docsC | Read, write, insert, and find-replace text in Google Docs documents. |
| manage_driveB | Search, upload, download, share, comment on, or manage files in Google Drive. |
| manage_emailC | Search, read, send, forward, or manage emails in a Google Workspace account. Supports Gmail search syntax. |
| manage_meetB | Browse past Google Meet conferences, participants, transcripts, recordings, and AI-generated smart notes. Requires Workspace Business Standard+ for transcripts/recordings. |
| manage_sheetsB | Read, write, and manage Google Sheets spreadsheets. |
| manage_tasksC | Manage task lists and tasks in Google Tasks. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Active Safety Policies | Current safety policies controlling what operations are allowed, blocked, or audited |
| Available Services | Google Workspace services and operations available through this server |
| Workspace Directory | File I/O workspace directory status and path |
| Server Version | Build version of the google-workspace-mcp server |
TDQS
Scored across 13 tools
Most tools target distinct Google Workspace services or resources, and descriptions clarify boundaries between email, calendar, drive, docs, sheets, contacts, tasks, and meet. However, queue_operations is an exact deprecated alias for bulk_operations, and bulk_operations/scratchpad overlap somewhat with individual service tools, creating minor selection ambiguity.
All tool names use snake_case, with service tools consistently following the manage_<resource> pattern. The meta tools bulk_operations and queue_operations also fit a predictable verb/noun convention, and the deprecated alias does not disrupt the naming scheme.
With 13 tools covering a broad Workspace suite, each major service area has a dedicated tool and the count is well-scoped. There is no excessive bloat, and the meta tools add useful orchestration without overwhelming the surface.
The server covers core Workspace workflows across Gmail, Calendar, Drive, Docs, Sheets, Contacts, Tasks, Meet, accounts, and bulk operations. Peripheral services like Slides, Forms, Chat, and Keep are missing, and Meet appears read-only, but the primary CRUD and lifecycle needs are well represented.