mcp-google-multi
Related Servers
Alternatives to mcp-google-multi
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables multi-user access to Google Workspace services (Gmail, Calendar, Docs, Sheets, Slides, Drive) via remote MCP with OAuth 2.1 authentication.-
- FlicenseBqualityDmaintenanceMCP server providing full access to Google Workspace services (Gmail, Drive, Calendar, Docs, Sheets, Slides, Forms, Tasks, Contacts) using OAuth authentication.1001-
- AlicenseCqualityAmaintenanceA multi-account Google Workspace MCP server that drives Gmail, Google Calendar, and Google Drive across any number of Google accounts in parallel from one server.422MIT
- AlicenseAqualityBmaintenanceEnables natural language interaction with multiple Google accounts (Gmail, Drive, Calendar) from MCP-compatible clients like Claude.6335 npm2MIT
- -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.-
- 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.3453 npm17MIT
TDQS
Scored across 19 tools
Each per-service discover tool targets a clearly named Google product (gmail, drive, sheets, docs, calendar, contacts, tasks, meet, searchconsole, workspaceevents), so an agent can pick the right one. The main overlaps are discover_all vs. the per-service discovers, and account_list vs. diagnose (both report token status), but descriptions frame these as bulk vs. targeted and registry vs. health, which resolves most confusion. google_api_search/google_api_call are explicitly positioned as an escape hatch, not a duplicate path.
Strong recurring patterns: *_discover for services, account_* for account management, google_api_* for the generic path, discover_all/discover_reset as a pair. Only 'diagnose' breaks the verb_noun convention, and the two discover_* names invert the pattern used by the service discovers, but both are still readable and predictable.
19 top-level tools is slightly above the comfortable band, but the discovery/collapse mechanism (discover_reset, discover_all) is purpose-built to keep context lean while exposing a very large hidden surface. Every visible tool earns a role: service gateways, escape hatch, account lifecycle, diagnostics.
Covers Gmail, Drive, Sheets, Docs, Calendar, Contacts, Tasks, Meet, Search Console and Workspace Events with read/write/delete operations, plus account add/reauth/config/diagnostics and a Discovery-based google_api_call escape hatch for any remaining REST method. No obvious dead ends for the stated Google Workspace purpose.