A
licenseB
qualityD
maintenanceProduction-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.
100
MIT
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
- 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.4,856 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.3414 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
B3.1/5.0
Scored across 120 tools
Disambiguation2/5
With 120 tools spanning 8+ Google Workspace products, many near-duplicate retrieval and editing tools blur together (e.g., get_doc_content vs get_doc_as_markdown vs get_drive_file_content; manage_drive_access vs set_drive_file_permissions; batch vs single Gmail message tools). Descriptions are rich, but an agent must track product, resource, and granularity to choose correctly, creating frequent misselection risk.
Naming Consistency3/5
All names are snake_case, but conventions are mixed: some tools use discrete verb_noun (create_doc, send_gmail_message), while others use manage_* for multi-action CRUD (manage_event, manage_contact, manage_drive_access). Product prefixes are also inconsistent—Gmail tools often use get_gmail_*, while Docs/Sheets tools often do not—though names remain readable.
Tool Count1/5
120 tools is far beyond the 3-15 well-scoped range and exceeds the 50+ extreme-mismatch threshold in the rubric. Even for a full Google Workspace suite, this volume causes tool-selection overload and suggests many granular operations should be consolidated.
Completeness4/5
Coverage is broad across Gmail, Calendar, Drive, Docs, Sheets, Slides, Chat, Forms, Tasks, Contacts, and Apps Script, with most core read/write actions present. Some lifecycle gaps remain (e.g., explicit delete tools for files/docs/sheets), but Drive metadata update/trash and import/export workarounds cover most workflows.
Maintenance
ActivityActive
ResponsivenessWithin a week