Google Workspace (GWS) MCP Server
Related Servers
Alternatives to Google Workspace (GWS) MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables AI agents to search, read, and compose Gmail, manage Drive files and Google Docs/Sheets/Slides, handle Calendar events and Tasks, and access Forms and Contacts using the official Workspace CLI, with credentials staying on the user's machine.38378 npmMIT
- AlicenseAqualityBmaintenanceExposes 38 tools that let AI agents search and read Gmail, draft and send messages, find and export Drive files, and work with Sheets, Docs, Slides, Calendar, Tasks, Forms and Contacts. It routes everything through Google's official Workspace CLI, so the user's own credential is created locally and never leaves their machine.381MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to control Google Workspace services (Slides, Docs, Sheets, Drive) with granular tools and provides a universal CLI escape hatch for all Workspace APIs.MIT
- AlicenseNot gradedqualityDmaintenanceProvides unified access to Google Workspace APIs including Gmail, Drive, Sheets, Calendar, Docs, Forms, and Chat through a single interface, enabling email management, file operations, spreadsheet editing, event scheduling, and more via natural language.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients like Claude Desktop and Cursor to interact with Google Docs, Sheets, and Drive, providing tools for reading, writing, formatting documents, managing spreadsheets, and searching Drive files.MIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Google Drive files and Google Sheets through search, read, and write operations. Supports automatic conversion of Google Workspace files to readable formats and direct spreadsheet cell updates.MIT
TDQS
Scored across 61 tools
Most tools are cleanly scoped to a resource+action within a clearly named product namespace (drive_files_*, sheets_values_*, calendar_events_*, tasks_tasks_*), so an agent can pick correctly in the common case. A few pairs need careful reading: drive_files_export vs drive_files_download, drive_files_update vs drive_files_copy, and the two ownership-transfer tools overlap conceptually (mitigated by very explicit descriptions).
The dominant pattern is product_resource_action in snake_case, but verbs are mixed (create vs insert: drive_files_create, docs_create, slides_create but tasks_tasks_insert, calendar_events_insert) and camelCase appears in several names (sheets_batchUpdate, slides_batchUpdate, docs_batchUpdate, slides_pages_getThumbnail, drive_permissions_transferOwnership). It remains readable and predictable per-product, but not a single consistent convention.
61 tools is far above the typical well-scoped range and makes the surface heavy to navigate, though the count is explained by bundling seven Google products (Drive, Docs, Sheets, Slides, Calendar, Gmail, Tasks). Each product's subset is reasonably sized, so the total is borderline rather than gratuitous.
Drive, Tasks, Calendar, and Slides have near-complete lifecycles, but Gmail is a notable hole: there is no send-message or send-draft tool, and label management is only partially exposed via gmail_threads_modify. Docs also lacks delete/move-style operations, forcing agents to route through Drive, and there is no tool to enumerate calendars or spreadsheets beyond Drive file listing.