Skip to main content
Glama

Related Servers

Alternatives to mcp-google-multi

No user-submitted related servers found.

    Related Servers

    TDQS

    A3.9/5.0

    Scored across 19 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data