Google Services MCP
Related Servers
Alternatives to Google Services MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to read and manage Google Workspace apps like Gmail, Drive, Docs, Sheets, and Calendar through 41 tools, with staged writes that require review and explicit commit before any change is applied.2MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to securely access Gmail, Google Sheets, and Google Docs with fine-grained, deny-by-default permissions, including read/write restrictions, send whitelists, and one-click approvals.-
- AlicenseNot gradedqualityCmaintenanceTurns Google Workspace into 45 MCP tools spanning Gmail, Drive, Calendar, Docs, Sheets, Slides, Chat, Tasks and Contacts, with server-side OAuth and a single bearer token so any AI client can read, send, create, and manage workspace content without a browser or Google SDK.MIT
- AlicenseNot gradedqualityDmaintenanceEnables natural language control over Google Workspace (Gmail, Drive, Calendar, Sheets, Slides, Tasks) through secure OAuth 2.1 authentication, with vault-level security and multi-user isolation.7-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to automate Google Drive tasks such as provisioning workspaces, reusing templates, inspecting folder structures, updating reports, and sharing files through user-controlled OAuth.MIT
- AlicenseAqualityBmaintenanceExposes 38 tools that let AI agents search and read Gmail, draft and send messages, find and export Drive files, and work with Sheets, Docs, Slides, Calendar, Tasks, Forms and Contacts. It routes everything through Google's official Workspace CLI, so the user's own credential is created locally and never leaves their machine.381MIT
TDQS
Scored across 44 tools
Within each service, tools mostly target distinct action/resource pairs, with clear separation between read, write, trash, and delete operations. A few read-only discovery tools overlap slightly (drive_list_files vs drive_search_files, sheets_read_range vs sheets_batch_read, gmail_list_threads vs gmail_search_messages), but descriptions help disambiguate.
Every tool follows a predictable snake_case pattern with a service prefix and verb/action phrase (calendar_, docs_, drive_, sheets_, gmail_). There are no mixed conventions or vague names, making the set highly predictable.
44 tools for a single MCP server is well beyond the typical well-scoped 3-15 range and exceeds the 25+ threshold for being too many. Although they are grouped by Google service, this surface is likely better split into per-service servers for reliable agent selection.
Core lifecycle coverage is strong across services: Calendar has full CRUD, Drive has read/write/trash/share, Sheets has range and tab operations, Gmail has search/draft/send/label operations, and Docs has create/read/edit. Gaps remain in Drive permission revocation/update, Gmail label creation/deletion and thread retrieval, and some Docs/Sheets lifecycle operations, but most core workflows are covered.