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.-
- AlicenseBqualityDmaintenanceProvides natural language control over Google Workspace services (Calendar, Drive, Gmail, Docs, Sheets, Slides, Forms, Tasks, Chat) via MCP, with OAuth 2.1 multi-user authentication.100MIT
- 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
- 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-
- AlicenseAqualityBmaintenanceEnables natural language interaction with multiple Google accounts (Gmail, Drive, Calendar) from MCP-compatible clients like Claude.632072MIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Google Workspace services (Gmail, Calendar, Drive, Docs, Sheets, Chat, Slides, People) through natural language using Claude Desktop, Claude Code CLI, and other MCP clients.4103MIT
TDQS
Scored across 114 tools
Multiple tools overlap significantly: list_drive_items and search_drive_files both list Drive files with similar filters, several Drive permission tools (get_drive_file_permissions, get_drive_shareable_link, check_drive_file_public_access, manage_drive_access, set_drive_file_permissions) cover the same sharing territory, and batch_update_doc duplicates modify_doc_text, find_and_replace_doc, insert_doc_elements, and tab management. While individual descriptions are detailed, an agent would often struggle to pick the right tool among these overlapping options.
Tool names are mostly snake_case with a verb_noun structure, but service prefixes are applied inconsistently: compare search_gmail_messages with generic search_messages and search_custom, or send_gmail_message with send_message. There is also a mixture of manage_*, modify_*, batch_update_*, and create_* patterns that, while readable, creates no strong predictable convention across the full set.
With 114 tools, this far exceeds the 50+ threshold for an extreme mismatch. The suite spans many Google services, but the count is bloated by redundant tools (batch_update_doc vs individual doc editors, overlapping Drive permission tools, manage_contact vs manage_contacts_batch) and would be far more usable split into per-service MCP servers.
Across the covered Google services, lifecycle coverage is generally strong: Gmail, Drive, Docs, Sheets, Calendar, Chat, Forms, Slides, Tasks, Contacts, Custom Search, and Apps Script all have read and write operations. Notable gaps exist—no calendar create/delete, no sheet deletion/rename, no permanent Drive delete—but these can often be worked around via existing tools like update_drive_file or Drive trash.