How to securely connect internal Cloud Run MCP servers to Gemini Enterprise Google Cloud published a reference architecture and companion GitHub repository (ge-secure-cloud-run-mcp) for connecting internal Cloud Run-hosted Model Context Protocol servers to Gemini Enterprise using Egress Agent Gateway, Private Service Connect, and FQDN-scoped Private Cloud DNS. The setup addresses three networking and security problems: routing from Gemini Enterprise's Google-managed tenant project into a serverless Cloud Run service, resolving .run.app hostnames privately so PSC traffic does not time out with HTTP 502, and validating the two authorization headers Gemini Enterprise sends on every request. The guidance scopes a Private Cloud DNS zone to the MCP service's exact FQDN rather than a wildcard *.run.app zone, so other Cloud Run services in a Shared VPC keep resolving normally. Enterprise teams adopting Gemini Enterprise https://cloud.google.com/gemini/enterprise/docs are increasingly building custom Model Context Protocol MCP https://modelcontextprotocol.io/ servers to connect AI agents with internal APIs, databases, and business workflows. Google Cloud Run https://cloud.google.com/run/docs is a natural fit for hosting these lightweight StreamableHTTP MCP servers: it scales automatically, manages TLS certificates out of the box, and integrates natively with Cloud IAM. However, moving a custom MCP server from an initial prototype to an enterprise production environment immediately introduces three real-world security and networking challenges: Here is how you can solve all three challenges using Egress Agent Gateway , Private Service Connect PSC , and FQDN-scoped Private Cloud DNS , complete with a runnable reference implementation and setup scripts on GitHub https://github.com/MagnIeeT/ge-secure-cloud-run-mcp . Connecting Gemini Enterprise which runs in a Google-managed tenant project to an internal serverless Cloud Run MCP server requires bridging two network hops and one scoped DNS lookup : Three Google Cloud networking and identity mechanisms work together in this architecture: Unlike a Compute Engine VM with an internal IP address inside your subnet, Cloud Run is serverless. Private routing therefore uses two bridges: When the Egress Agent Gateway receives a tool call for your Cloud Run MCP server URL, it resolves the hostname once before injecting the packet into your VPC. Without Private Cloud DNS, public DNS resolves .run.app domains to public internet IPs, which time out HTTP 502 because a PSC Network Attachment does not route out to the public internet. Instead of creating a wildcard .run.app private zone, which would override DNS resolution for every Cloud Run service in a Shared VPC, you create a Private Cloud DNS zone scoped exclusively to your MCP service's exact fully qualified domain name FQDN and peer only that domain with the Agent Gateway. Because Cloud DNS uses longest-suffix matching, every other Cloud Run service in your Shared VPC continues resolving normally. Meanwhile, the Agent Gateway opens its HTTPS connection to the private VIP 199.36.153.8 or 240.0.0.10 while preserving your Cloud Run service hostname in the TLS SNI and HTTP Host header so Cloud Run routes the request to your exact container. When connecting to a Cloud Run MCP server URL, Gemini Enterprise sends two distinct authorization headers on every request: class OAuth2ValidationMiddleware BaseHTTPMiddleware : """Validates the end-user OAuth 2.0 Bearer token on incoming MCP requests.""" async def dispatch self, request: Request, call next - Response: if request.url.path == "/health": return await call next request has serverless auth = "x-serverless-authorization" in request.headers auth header = request.headers.get "authorization", "" if auth header.lower .startswith "bearer " : raw token = auth header.split " ", 1 1 .strip verified = await verify google oauth token raw token if verified is None and REQUIRE OAUTH: return JSONResponse {"error": "Invalid or expired OAuth 2.0 Bearer token."}, status code=401, elif REQUIRE OAUTH: return JSONResponse {"error": "Missing Authorization: Bearer