Google Cloud Docs MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_google_cloud_docA | Fetch and extract content from a specific Google Cloud documentation page. WHEN TO USE: Use this tool when you already know the exact documentation path you need, or when you want to get detailed content from a specific GCP documentation page. INPUT: Documentation path after cloud.google.com/ (e.g., 'compute/docs/instances/create-start-instance', 'storage/docs/creating-buckets') OUTPUT: Returns JSON with:
COMMON PATHS:
TIP: If you don't know the exact path, use 'search_google_cloud_docs' first to find relevant documentation. |
| search_google_cloud_docsA | Search Google Cloud documentation with any free-form query. Returns relevant documentation with actual content. WHEN TO USE: ALWAYS use this tool when the user asks about Google Cloud Platform (GCP) services, configurations, best practices, or how-to questions. This is the PRIMARY tool for GCP-related queries. TRIGGERS - Use this tool when user asks about:
INPUT:
EXAMPLE QUERIES:
OUTPUT: Returns JSON with:
SUPPORTED TOPICS (80+ mappings):
|
| list_google_cloud_productsA | List all available Google Cloud products with their documentation paths. WHEN TO USE: Use this tool when:
OUTPUT: Returns JSON with:
PRODUCTS INCLUDED (20+):
TIP: Use the returned 'docsPath' with 'fetch_google_cloud_doc' to get detailed documentation. |
| get_api_referenceA | Get REST API reference documentation for a specific Google Cloud service. WHEN TO USE: Use this tool when:
INPUT:
SUPPORTED SERVICES & RESOURCES:
OUTPUT: Returns JSON with:
EXAMPLE USAGE:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
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.
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.
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.
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.