Google Workspace MCP Server - Control Gmail, Calendar, Docs, Sheets, Slides, Chat, Forms & Drive
Related Servers
Alternatives to Google Workspace MCP Server - Control Gmail, Calendar, Docs, Sheets, Slides, Chat, Forms & Drive
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceProduction-ready MCP server for Google Workspace providing broad coverage across Gmail, Drive, Calendar, Docs, Sheets, and more, with safe-by-default write operations and markdown-to-Google-Docs support.100MIT
- AlicenseBqualityCmaintenanceComprehensive Google Workspace MCP server with Gmail, Drive, Calendar, and Contacts integration.2614 npmMIT
- AlicenseNot gradedqualityAmaintenanceProvides a comprehensive Google Workspace MCP server with deep features including raw formula access, structural Docs support, and complete Drive and Calendar coverage.2,342 PyPIMIT
- AlicenseAqualityDmaintenanceMCP server for Google Workspace APIs - Docs, Sheets, Drive, Gmail, and Calendar. Enables reading, creating, and editing Google Docs and Sheets, managing comments, reading emails, and viewing calendar events.3424 npm17MIT
- FlicenseBqualityDmaintenanceMCP server providing full access to Google Workspace services (Gmail, Drive, Calendar, Docs, Sheets, Slides, Forms, Tasks, Contacts) using OAuth authentication.1001-
- AlicenseNot gradedqualityBmaintenanceA set of five independent MCP servers for Google Workspace (Gmail, Calendar, Drive, Sheets, Docs) enabling secure access and management of email, calendar events, files, spreadsheets, and documents. Features OAuth 2.1 with per-resource tokens and uses stable Google product APIs.MIT
TDQS
Scored across 121 tools
Many tools have unclear boundaries due to near-duplicate batch/single variants and overlapping resource accessors (e.g., get_doc_content vs get_doc_as_markdown vs get_drive_file_content; manage_contact vs manage_contacts_batch). Descriptions are detailed, but an agent could easily select the wrong tool for a task.
The naming is mostly snake_case verb_noun, but the verb vocabulary is inconsistent: get/list/search/read, create/insert/add, modify/update/manage/set are used interchangeably. Singular/plural mismatches like manage_event vs manage_contact and get_task vs get_task_list further weaken consistency.
At 121 tools, this is far beyond the 3-15 well-scoped range and clearly in the 50+ extreme category. The set is bloated with batch variants, consolidated/manage tools, debug helpers, and auth utilities, which makes the surface overwhelming for an agent.
The server covers core operations across Gmail, Calendar, Docs, Sheets, Slides, Forms, Chat, Drive, Tasks, Contacts, and Apps Script, with few obvious dead ends. Minor gaps exist, such as no dedicated calendar deletion or form deletion, but these can generally be worked around via Drive metadata or API limitations.