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.6320 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.346 npm17MIT
TDQS
Scored across 19 tools
The set has clear seams: per-service `<service>_discover` catalogs, `account_*` lifecycle tools, `google_api_search`/`google_api_call` escape hatches, and `diagnose`. The only mild overlap is between `discover_all` and the per-service discovers (and `discover_reset`), but descriptions explicitly frame these as reveal-all / reveal-one / collapse-back, so an agent can pick correctly.
Consistent sub-groups exist: ten `<service>_discover` tools, four `account_*` tools, `google_api_search`/`google_api_call`, and `discover_all`/`discover_reset`. The only friction is verb placement varying across groups (gmail_discover is noun_verb, while account_list and discover_all are verb_noun), but each family is internally predictable.
19 tools is slightly above the ideal band, but the count is justified by genuine multi-service breadth (Gmail, Drive, Calendar, Sheets, Docs, Contacts, Tasks, Meet, Search Console, Workspace Events) plus account/auth plumbing. Progressive disclosure means the effective surface stays small, so each tool earns its slot.
Coverage is broad: account add/list/reauth/config-write, health diagnostics, discovery control, generic REST search/call, and per-service catalogs covering the core Workspace apps. The main gap is account lifecycle teardown (no account_remove/delete or explicit default-account switching), plus services like Chat/Keep only reachable via `google_api_call` rather than curated tools.