Google Workspace MCP Server
Related Servers
Alternatives to Google Workspace MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceFull natural language control over Google Calendar, Drive, Gmail, Docs, Sheets, Slides, Forms, Tasks, Contacts, and Chat through MCP clients.100MIT
- -licenseNot gradedqualityNot gradedmaintenanceProvides natural language control over Google Workspace services including Gmail, Drive, Calendar, Docs, Sheets, Slides, Forms, Tasks, Contacts, and Chat through all MCP clients.-
- FlicenseBqualityCmaintenanceMCP server providing full Google Workspace access (Gmail, Drive, Calendar, Docs, Sheets, Slides, Forms, Tasks, Contacts) using your own OAuth credentials, enabling natural language management of Google services.100-
- AlicenseNot gradedqualityAmaintenanceEnables management of Google Drive files, Docs, Sheets, Slides, and Calendar events through natural language using the MCP protocol.15,427 npm220MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read and write across Google Workspace services, including Calendar, Tasks, Gmail, Drive, Docs, Sheets, and Contacts, through a unified MCP interface.3MIT
- AlicenseBqualityAmaintenanceMCP server integrating multiple Google Workspace services including Gmail, Calendar, Drive, Sheets, Docs, Tasks, People, Forms, and Slides, enabling users to manage emails, events, files, documents, and more through natural language.15MIT
TDQS
Scored across 124 tools
Most tools are cleanly separated by Google service and resource, but there are several confusable pairs: get_drive_file_content and get_doc_content both fetch file content by ID, search_drive_files and search_docs overlap, and set_drive_file_permissions vs. manage_drive_access blur the permission-management boundary. The long, detailed descriptions help agents choose correctly, so the overlap is manageable rather than severe.
The set overwhelmingly follows a lowercase snake_case verb_noun pattern with useful service prefixes such as gmail_, drive_, doc_, and script_. Minor deviations like search_custom, set_publish_settings, get_messages, and debug_docs_runtime_info break the otherwise predictable convention, but the overall pattern is still clear.
With 124 tools, this server is far beyond the 50+ extreme threshold and would overwhelm an agent's tool-selection space. The breadth reflects the many Google Workspace services, but as a single coherent MCP tool set it is drastically over-scoped.
Coverage is impressively broad across Gmail, Drive, Calendar, Docs, Sheets, Chat, Forms, Slides, Tasks, Contacts, Search, and Apps Script. However, there are notable gaps: no Drive delete/trash operation exists, which also prevents agents from deleting Docs, Sheets, and Slides files, and calendar metadata management is essentially create-only.