Google Cloud Docs MCP Server
Provides access to Google Cloud Platform documentation through search and content extraction tools, supporting 20+ GCP products including Compute Engine, Cloud Storage, BigQuery, GKE, Cloud Functions, and more. Enables querying documentation with natural language, fetching specific documentation pages, listing supported products, and accessing REST API references.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Google Cloud Docs MCP Server how to set up a Cloud Storage bucket with CMEK encryption"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Google Cloud Docs MCP Server
An MCP (Model Context Protocol) server that provides AI assistants with access to Google Cloud Platform documentation. This enables Claude and other MCP-compatible assistants to search, fetch, and understand GCP documentation in real-time.
Table of Contents
Related MCP server: GCP MCP
Features
Free-form Search: Search GCP documentation with natural language queries
Content Extraction: Extract clean markdown content from documentation pages
80+ Topic Mappings: Pre-configured mappings for common GCP topics
Relevance Scoring: Smart ranking of search results by relevance
API Reference: Access REST API documentation for GCP services
20+ GCP Products: Support for major Google Cloud services
How It Works
┌─────────────┐ ┌─────────────────┐ ┌──────────────────┐
│ Claude │────▶│ MCP Server │────▶│ Google Cloud │
│ (or other │ │ (this project) │ │ Documentation │
│ MCP client)│◀────│ │◀────│ (cloud.google │
└─────────────┘ └─────────────────┘ │ .com/docs) │
└──────────────────┘Query Processing: When Claude receives a GCP-related question, it calls the MCP server tools
Search Strategy: The server uses a multi-step search approach:
Google Search targeting
site:cloud.google.comGoogle Cloud's internal search API (fallback)
80+ pre-configured topic mappings (fallback)
Content Extraction: Uses Cheerio to parse HTML and extract clean markdown
Relevance Scoring: Results are scored and sorted by query relevance
Response: Returns structured JSON with documentation content
Technical Details
Protocol: MCP (Model Context Protocol) over stdio transport
Content Parsing: HTML to Markdown conversion with Cheerio
Search: Combines Google Search scraping with fallback topic mappings
Output Format: Structured JSON with markdown content
Prerequisites
Node.js >= 18.0.0
npm or yarn
Claude Desktop, Claude Code, or other MCP-compatible client
Installation
From Source
# Clone the repository
git clone https://github.com/longngo192/gcpdoc-mcp
cd gcpdoc-mcp
# Install dependencies
npm install
# Build the project
npm run buildQuick Start
npm install && npm run buildConfiguration
Claude Desktop
Add to your Claude Desktop config file:
Windows: %APPDATA%\Claude\claude_desktop_config.json
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"google-cloud-docs": {
"command": "node",
"args": [
"/path/to/google-cloud-docs-mcp/dist/index.js"
]
}
}
}Claude Code CLI
# Add the MCP server
claude mcp add google-cloud-docs -- node /path/to/dist/index.js
# Verify installation
claude mcp listUsage
Once configured, Claude will automatically use the GCP documentation tools when you ask questions about Google Cloud services.
Example Queries
"How do I set up VPC peering between two GCP projects?"
"What are the steps to enable CMEK encryption for Cloud Storage?"
"How to configure Cloud SQL high availability?"
"Show me GKE autoscaling configuration options"
"How to set environment variables in Cloud Run?"Direct Tool Usage
If using MCP protocol directly:
// Search documentation
{
"method": "tools/call",
"params": {
"name": "search_google_cloud_docs",
"arguments": {
"query": "vpc peering between projects"
}
}
}
// Fetch specific documentation
{
"method": "tools/call",
"params": {
"name": "fetch_google_cloud_doc",
"arguments": {
"path": "vpc/docs/vpc-peering"
}
}
}Available Tools
1. search_google_cloud_docs
Search GCP documentation with free-form queries. Primary tool for GCP questions.
Parameter | Type | Required | Description |
| string | Yes | Natural language search query |
| string | No | Filter by GCP product (e.g., 'compute', 'storage') |
Example:
{
"query": "how to share encrypted bucket cross account",
"product": "storage"
}2. fetch_google_cloud_doc
Fetch content from a specific documentation page.
Parameter | Type | Required | Description |
| string | Yes | Documentation path after |
Example:
{
"path": "storage/docs/encryption/customer-managed-keys"
}3. list_google_cloud_products
List all supported GCP products and their documentation paths.
No parameters required.
4. get_api_reference
Get REST API reference for a GCP service.
Parameter | Type | Required | Description |
| string | Yes | Service name (e.g., 'compute', 'storage') |
| string | No | Specific API resource (e.g., 'instances', 'buckets') |
Example:
{
"service": "compute",
"resource": "instances"
}Supported Topics
The server includes 80+ topic mappings for accurate search results:
Category | Topics |
Storage & Encryption | encrypt, bucket, cmek, kms, customer managed, object storage |
IAM & Security | iam, role, service account, impersonation, workload identity |
Networking | vpc, peering, shared vpc, firewall, load balancer, dns, nat |
Database | cloud sql, high availability, mysql, postgres, replica, failover |
BigQuery | partition, cluster, materialized view, schedule |
GKE | gke, autoscaling, node pool, horizontal pod autoscaler, helm |
Serverless | cloud run, environment variable, cloud function, deploy |
Container | docker, artifact registry, cloud build |
Pub/Sub | pubsub, topic, subscription |
Data Processing | dataflow, dataproc, composer, airflow, spark |
Monitoring | logging, monitoring, metric, alert, dashboard, trace |
Infrastructure | terraform, deployment manager, gcloud |
Supported GCP Products
ID | Name | Description |
| Compute Engine | Virtual machines and infrastructure |
| Cloud Storage | Object storage service |
| BigQuery | Data warehouse and analytics |
| GKE | Managed Kubernetes service |
| Cloud Functions | Serverless compute platform |
| Cloud Run | Serverless containers |
| Pub/Sub | Messaging and event ingestion |
| Cloud SQL | Managed relational databases |
| Firestore | NoSQL document database |
| Cloud Spanner | Globally distributed database |
| Vertex AI | Machine learning platform |
| IAM | Identity and Access Management |
| VPC | Virtual Private Cloud networking |
| Cloud Load Balancing | Global load balancing |
| Cloud Logging | Log management and analysis |
| Cloud Monitoring | Infrastructure monitoring |
Project Structure
google-cloud-docs-mcp/
├── src/
│ └── index.ts # Main MCP server implementation
├── dist/ # Compiled JavaScript (generated)
├── package.json # Project configuration
├── tsconfig.json # TypeScript configuration
├── .gitignore # Git ignore rules
├── LICENSE # MIT License
└── README.md # This fileDevelopment
Running in Development Mode
# With hot reload
npm run dev
# Build and run
npm run build && npm startTesting the Server
# Test MCP initialization
echo '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"1.0"}}}' | node dist/index.js
# Test tools/list
echo '{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}' | node dist/index.jsBuilding
npm run buildContributing
Contributions are welcome! Here's how you can help:
Getting Started
Fork the repository
Clone your fork:
git clone https://github.com/yourusername/google-cloud-docs-mcp.gitCreate a feature branch:
git checkout -b feature/your-feature-nameMake your changes
Run tests and build:
npm run buildCommit your changes:
git commit -m "Add your feature"Push to your fork:
git push origin feature/your-feature-nameOpen a Pull Request
Contribution Ideas
Add more topic mappings: Expand the
topicMappingsobject insrc/index.tsSupport more GCP products: Add entries to
GOOGLE_CLOUD_PRODUCTSImprove content extraction: Enhance the Cheerio parsing logic
Add caching: Implement response caching to reduce API calls
Add tests: Write unit tests for search and content extraction
Documentation: Improve README or add usage examples
Code Style
Use TypeScript
Follow existing code patterns
Add comments for complex logic
Test your changes before submitting
Reporting Issues
Found a bug or have a suggestion? Please open an issue with:
Clear description of the problem
Steps to reproduce
Expected vs actual behavior
Your environment (Node.js version, OS)
Acknowledgments
Model Context Protocol - The protocol that enables AI-tool communication
Cheerio - Fast HTML parsing
Google Cloud Documentation - The source of all documentation
License
This project is licensed under the MIT License - see the LICENSE file for details.
Made with love for the GCP and AI community
Available Tools
4 toolsfetch_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:
title: Page title
url: Full URL
content: Markdown-formatted documentation content (max 20,000 chars)
contentLength: Total content length
truncated: Whether content was truncated
COMMON PATHS:
Compute: compute/docs/instances/create-start-instance
Storage: storage/docs/creating-buckets, storage/docs/encryption
BigQuery: bigquery/docs/partitioned-tables, bigquery/docs/clustered-tables
Cloud SQL: sql/docs/high-availability, sql/docs/replication
GKE: kubernetes-engine/docs/how-to/cluster-autoscaler
IAM: iam/docs/understanding-roles, iam/docs/service-accounts
VPC: vpc/docs/vpc-peering, vpc/docs/shared-vpc
Cloud Run: run/docs/configuring/environment-variables
TIP: If you don't know the exact path, use 'search_google_cloud_docs' first to find relevant documentation.
Inputs: path (required).
get_api_referenceA
Get REST API reference documentation for a specific Google Cloud service.
WHEN TO USE: Use this tool when:
User needs API endpoints, methods, or parameters
User is developing integrations with GCP APIs
User asks about REST API for a specific GCP service
User needs to know available API resources for a service
INPUT:
service (required): GCP service name (compute, storage, bigquery, pubsub, sql, kubernetes, functions, run, iam)
resource (optional): Specific API resource (instances, buckets, datasets, topics, etc.)
SUPPORTED SERVICES & RESOURCES:
compute: instances, disks, networks, firewalls, images, machineTypes
storage: buckets, objects, notifications
bigquery: datasets, tables, jobs, routines
pubsub: topics, subscriptions, snapshots
sql: instances, databases, users, backupRuns
kubernetes: clusters, nodePools, operations
functions: functions, operations, locations
run: services, configurations, routes, revisions
iam: roles, serviceAccounts, policies
OUTPUT: Returns JSON with:
service: Service name
description: Service description
apiReferenceUrl: Full URL to API reference
availableResources: List of available resources for this service
documentation: Actual API documentation content (if available)
EXAMPLE USAGE:
Get Compute Engine API overview: service="compute"
Get Storage buckets API: service="storage", resource="buckets"
Get BigQuery datasets API: service="bigquery", resource="datasets"
Inputs: service (required), resource.
list_google_cloud_productsA
List all available Google Cloud products with their documentation paths.
WHEN TO USE: Use this tool when:
User wants to see what GCP services are available
User is exploring GCP products
You need to find the correct product ID for other tools
User asks "what GCP services are there?" or similar
OUTPUT: Returns JSON with:
totalProducts: Number of products listed
products: Array of products with id, name, docsPath, docsUrl, description
PRODUCTS INCLUDED (20+):
Compute: compute, kubernetes, functions, run, appengine
Storage: storage, firestore, spanner
Database: sql, bigquery
AI/ML: ai (Vertex AI), vision, speech, translate
Networking: vpc, loadbalancing, cdn, dns
Security: iam, kms
Messaging: pubsub
Monitoring: logging, monitoring
TIP: Use the returned 'docsPath' with 'fetch_google_cloud_doc' to get detailed documentation.
Inputs: no named parameters.
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:
Any GCP service (Compute Engine, Cloud Storage, BigQuery, Cloud SQL, GKE, Cloud Run, IAM, VPC, etc.)
Configuration questions ("how to configure...", "how to setup...")
Best practices for GCP services
Troubleshooting GCP issues
Cross-project or cross-account scenarios
Security, encryption, permissions in GCP
Networking in GCP (VPC, peering, firewall, load balancer)
Database configurations (Cloud SQL HA, replicas, backups)
Container orchestration (GKE autoscaling, node pools)
Serverless (Cloud Run, Cloud Functions environment variables)
INPUT:
query (required): Free-form search query in natural language
product (optional): Filter by specific GCP product
EXAMPLE QUERIES:
"how to share encrypted bucket cross account"
"vpc peering between two projects"
"cloud sql high availability setup"
"gke autoscaling configuration"
"bigquery partition table"
"cloud run environment variables"
"iam service account impersonation"
"cloud storage cmek encryption"
"gke workload identity"
OUTPUT: Returns JSON with:
query: Original search query
totalResults: Number of results found
results: Array of top 3 docs with full content (title, url, content)
otherRelatedDocs: Additional related documentation URLs
SUPPORTED TOPICS (80+ mappings):
Storage & Encryption: encrypt, bucket, cmek, kms, customer managed, object storage
IAM & Security: iam, role, service account, impersonation, workload identity
Networking: vpc, peering, shared vpc, firewall, load balancer, dns, nat, private access
Database: cloud sql, high availability, mysql, postgres, replica, failover
BigQuery: partition, cluster, materialized view, schedule
GKE: gke, autoscaling, node pool, horizontal pod autoscaler, helm
Serverless: cloud run, environment variable, cloud function, deploy
Container: docker, artifact registry, cloud build
Pub/Sub: pubsub, topic, subscription
Data Processing: dataflow, dataproc, composer, airflow, spark
Monitoring: logging, monitoring, metric, alert, dashboard, trace
Infrastructure: terraform, deployment manager, gcloud
Inputs: query (required), product.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Provides tools for searching Google Workspace documentation and much more.
Versioned documentation registry and semantic search for AI tools and coding assistants.
Provide your AI coding tools with token-efficient access to up-to-date technical documentation for…
The Google GKE MCP server is a managed Model Context Protocol server that provides AI applications with tools to manage Google Kubernetes Engine (GKE) clusters and Kubernetes resources. It exposes a structured, discoverable interface that allows AI agents to interact with GKE and Kubernetes APIs, enabling them to inspect cluster configurations, retrieve Kubernetes resource YAMLs, monitor operations like cluster upgrades, diagnose issues, and optimize costs—all without needing to parse text output or use complex kubectl commands.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables 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.16MIT
- AlicenseCqualityDmaintenanceEnables 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.91,244 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables 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.1MIT
- AlicenseAqualityCmaintenanceProvides 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.7190 npm7MIT