Google Cloud Docs MCP Proxy
Provides access to Google Cloud documentation, enabling AI agents to search and retrieve official Google Cloud documentation content.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Google Cloud Docs MCP Proxy
This repository contains a proxy for Google Cloud Documentation MCP Server.
Google required authenticated access to the MCP server, so this proxy is used to bypass that requirement and allow unauthenticated access to the documentation.
It is available using MIT license, so feel free to use it in your own projects.
Setup
Go is required to build and run the proxy locally.
Authenticate with Google Application Default Credentials, for example:
gcloud auth application-default loginThe Developer Knowledge API must be enabled on the target project:
gcloud services enable developerknowledge.googleapis.com --project PROJECT_IDWhen the proxy runs using ADC authentication, it calls the MCP server as the logged-in user, so that user needs the MCP Tool User role (roles/mcp.toolUser, permission mcp.tools.call) on the target project:
gcloud projects add-iam-policy-binding PROJECT_ID \
--member="user:USER_EMAIL" --role="roles/mcp.toolUser"When the proxy runs with a service account key (--key-file in scripts/start.sh and scripts/start_container.sh), it calls the MCP server as the service account, so the service account needs the same role:
gcloud projects add-iam-policy-binding PROJECT_ID \
--member="serviceAccount:SA_EMAIL" --role="roles/mcp.toolUser"Related MCP server: docs-to-mcp
Configuration
The proxy is configured using environment variables:
MCP_TARGET_URL: MCP server endpoint to forward requests to. Defaults tohttps://developerknowledge.googleapis.com/mcp.PROXY_HOST: listen address. Defaults to0.0.0.0.PROXY_PORT: listen port. Defaults to8989.
Running locally
go run .Point your MCP client at http://localhost:8989/.
Authentication diagnostics
GET /_diagnostics/auth reports the status of the ADC credentials used to authenticate to the MCP server: credential type, quota project, scopes, token validity and expiry, and any error encountered while refreshing the token. It does not expose the access token itself.
Running as a container
docker build -t gcp-docs-mcp-proxy .
docker run -p 8989:8989 -v "$HOME/.config/gcloud:/root/.config/gcloud:ro" gcp-docs-mcp-proxyThe image is built on gcr.io/distroless/static-debian13.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Agent-native MCP server over the public saagarpatel.dev corpus. Read-only, stateless.
Team docs served to AI agents over MCP - search, Markdown reads, version pinning, read audit.
Read-only MCP access to devplane.dev's public pages, FAQ corpus and comparisons.
Read-only MCP server for the OrchestKit docs: full-text search + Markdown fetch. No auth.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceProvides RAG (Retrieval Augmented Generation) access to technical documentation through MCP, enabling LLMs to search and retrieve relevant documentation on-demand.5MIT
- AlicenseAqualityDmaintenanceEnables searching and retrieving documentation from crawled documentation sites as an MCP server, allowing coding agents to query real docs instead of relying on training data.4MIT
- FlicenseNot gradedqualityBmaintenanceEnables MCP-based access to Adhoc documentation, providing search, content retrieval, and feedback issue creation with audience gating and leak protection.-
- AlicenseNot gradedqualityBmaintenanceEnables programming agents to retrieve internal R&D documentation with traceable, reproducible evidence through the MCP protocol, supporting multi-corpus routing and access control.1MIT