Skip to main content
Glama
thrix

gcloud-workspace-mcp

by thrix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to gcloud-workspace-mcp

No user-submitted related servers found.

    Related Servers

    • Google Workspace MCP

      thenavidm
      A
      license
      B
      quality
      A
      maintenance
      Enables AI agents to search, read, and compose Gmail, manage Drive files and Google Docs/Sheets/Slides, handle Calendar events and Tasks, and access Forms and Contacts using the official Workspace CLI, with credentials staying on the user's machine.
      38
      58 npm
      MIT

    • Google Workspace MCP Server

      apexlogicfocus
      A
      license
      A
      quality
      B
      maintenance
      Exposes 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.
      38
      58 npm
      1
      MIT

    • SCD MCP Docs

      FabrizioID
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients like Claude Desktop and Cursor to interact with Google Docs, Sheets, and Drive, providing tools for reading, writing, formatting documents, managing spreadsheets, and searching Drive files.
      MIT

    • mcp-google_docs

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables reading, creating, and editing Google Docs via OAuth. Supports tools for retrieving, inserting, appending, and replacing text in documents.
      13 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a clearly distinct service, resource, and action: Drive search, Drive metadata lookup, Google-native export, non-native download, Gmail search, message fetch, and thread fetch. The descriptions explicitly delineate Google-native files (docs_export) from uploaded files (drive_download) and single messages from threads, so misselection is unlikely.

    Naming Consistency4/5

    The set follows a predictable service_action pattern (drive_search, drive_get_metadata, gmail_get_message, gmail_get_thread), with only a minor deviation in docs_export using the 'docs' prefix instead of 'drive'. The convention is still readable and nearly uniform throughout.

    Tool Count5/5

    Seven tools is well-scoped for a read/search/export-focused Drive, Docs, and Gmail integration. Each tool has a distinct purpose, and there are no redundant or filler operations.

    Completeness4/5

    The surface covers the core read-only lifecycle: searching and fetching Drive metadata, exporting Google-native documents, downloading non-native files, and searching/fetching Gmail messages and threads. Minor gaps remain, such as direct Gmail attachment extraction or fuller Sheets multi-sheet export, but described workarounds (raw .eml, CSV first sheet) make these manageable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources