Skip to main content
Glama
longngo192

Google Cloud Docs MCP Server

by longngo192
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Google Cloud Docs MCP Server

No user-submitted related servers found.

    Related Servers

    • GCP MCP

      RadiumGu
      A
      license
      C
      quality
      D
      maintenance
      Enables AI assistants to interact with Google Cloud Platform resources through natural language queries. Supports querying and managing GCP services like Compute Engine, Cloud Storage, BigQuery, and more across multiple projects and regions.
      9
      1,740 npm
      MIT

    • Google AI Search MCP

      shariqriazz
      A
      license
      A
      quality
      B
      maintenance
      Provides AI-powered search and documentation tools using Google Vertex AI or Gemini API with real-time web search grounding, enabling technical queries, code analysis, documentation retrieval, and architecture recommendations to overcome LLM knowledge gaps.
      7
      101 npm
      6
      MIT

    • Multi-Source Documentation MCP

      florinel-chis
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to search and query documentation from multiple sources including Voiceflow and Claude Code, with full-text search, code examples retrieval, and step-by-step tutorials access.
      1
      MIT

    • Crawl4AI RAG MCP Server

      adnan0758
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to crawl, index, and retrieve information from technical documentation using semantic search, with optional knowledge graph validation for code hallucination detection.
      MIT

    • GCP MCP Server

      enesbol
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to interact with and manage Google Cloud Platform resources including Compute Engine, Cloud Run, Storage, BigQuery, and other GCP services through a standardized MCP interface.
      1
      6
      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.6/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: fetch_google_cloud_doc retrieves specific documentation pages, get_api_reference provides API details, list_google_cloud_products enumerates available services, and search_google_cloud_docs performs general searches. The descriptions explicitly differentiate when to use each tool, preventing confusion.

    Naming Consistency5/5

    All tool names follow a consistent snake_case pattern with a clear verb_noun structure (fetch_google_cloud_doc, get_api_reference, list_google_cloud_products, search_google_cloud_docs). The naming is uniform and predictable across the set, making it easy for agents to understand and select tools.

    Tool Count5/5

    With 4 tools, the server is well-scoped for its purpose of accessing Google Cloud documentation and APIs. Each tool serves a unique function (fetching, searching, listing, and API reference), and the count is neither too sparse nor overwhelming, fitting typical MCP server ranges.

    Completeness5/5

    The tool set comprehensively covers the domain of Google Cloud documentation access: it supports fetching specific docs, searching broadly, listing products for exploration, and retrieving API references. There are no obvious gaps, as the tools enable agents to find, access, and understand GCP resources effectively.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources