Google Workspace MCP Server
Related Servers
Alternatives to Google Workspace MCP Server
No user-submitted related servers found.
Related Servers
- -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.-
- AlicenseNot gradedqualityAmaintenanceEnables management of Google Drive files, Docs, Sheets, Slides, and Calendar events through natural language using the MCP protocol.8,493 npm219MIT
- 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-
- AlicenseBqualityDmaintenanceEnables natural language control over Google Workspace services including Gmail, Calendar, Drive, Docs, Sheets, Slides, Forms, Tasks, Chat, Contacts, Apps Script, and Custom Search via a remote MCP server hosted on Google Cloud Run.114MIT
- FlicenseNot gradedqualityBmaintenanceEnables multi-user access to Google Workspace services (Gmail, Calendar, Docs, Sheets, Slides, Drive) via remote MCP with OAuth 2.1 authentication.-
- AlicenseAqualityBmaintenanceEnables natural language interaction with multiple Google accounts (Gmail, Drive, Calendar) from MCP-compatible clients like Claude.63189 npm2MIT
TDQS
Scored across 105 tools
Multiple tools have overlapping purposes, such as get_doc_content and get_drive_file_content both retrieving file content, and search_docs vs search_drive_files with redundant functionality. While descriptions are detailed, the boundaries between these pairs and others (e.g., permission-related Drive tools) are not clearly distinct, making misselection likely.
Most tools follow a verb_noun pattern, but there are notable inconsistencies: 'modify_event' instead of 'update_event', 'doc' vs 'document' prefixes (get_doc_content vs read_document_comments), and 'create_meeting_with_zoom' breaking the pattern. Overall, the naming is readable but not fully consistent.
With 105 tools, the server is heavily overloaded, far exceeding the typical 3-15 well-scoped range. The broad coverage of Google services justifies a larger set, but the sheer number still makes it difficult for an agent to choose appropriately and may include redundant tools.
The tool set covers most core workflows across Gmail, Calendar, Drive, Docs, Sheets, Slides, Tasks, and Chat, but there are notable gaps: Forms lacks update/delete operations, and Zoom lacks an update meeting tool. These gaps will require workarounds for full lifecycle management.