Google releases tutorial on securely connecting internal Cloud Run MCP servers
Understand this story
Google has released a tutorial and reference implementation on how to connect an internal-only Cloud Run MCP server to Gemini Enterprise. The solution combines the Egress Agent Gateway, Private Service Connect, and FQDN-restricted Private Cloud DNS, and provides a runnable reference implementation and installation scripts on GitHub. Google says enterprise security policies require internal MCP servers to block all public internet traffic and accept only requests from private VPC networks; however, when Cloud Run enables internal ingress, Gemini Enterprise's default public calls are rejected with an HTTP 404 at Google's edge. Google also says production deployments require two independent identity checks for every tool call; if the entire *.run.app domain is overridden for a single MCP server, it could hijack DNS resolution and break routing for other Cloud Run services on that network.
AI overview based on source reports · Updated 56 min ago
Coverage timeline
Follow the coverage to explore different perspectives.
- Google Developers BlogHow to securely connect internal Cloud Run MCP servers to Gemini Enterprise
Google Cloud explains how to connect Gemini Enterprise to internal-only Cloud Run MCP servers using an Egress Agent Gateway, Private Service Connect, and FQDN-scoped Private Cloud DNS, addressing internal ingress, dual service and user authentication, and Shared VPC DNS collisions. The post details a two-bridge private VPC routing design, dual-header identity checks (Cloud Run IAM OIDC plus user OAuth 2.0), and a five-step setup, with a reference implementation and scripts on GitHub.
Activity for this story
Not enough continuous observations to show a trend yet.