Google details private MCP connectivity for Gemini Enterprise
Google Developers Blog published a guide for connecting Gemini Enterprise agents to internal StreamableHTTP MCP servers hosted on Google Cloud Run. The reference architecture combines Egress Agent Gateway, Private Service Connect and FQDN-scoped Cloud DNS with dual service and user authentication, and includes a Python server, middleware and deployment scripts. Google says internal-only ingress blocks default public Gemini Enterprise calls with an HTTP 404 at Google’s edge.
The guide provides a concrete implementation pattern for exposing enterprise MCP tools through private networking while validating both the Gemini Enterprise service identity and the signed-in user’s OAuth 2.0 access token.
How to securely connect internal Cloud Run MCP servers to Gemini Enterprise - Google Developers Blog
How to securely connect internal Cloud Run MCP servers to Gemini Enterprise
NOV. 20, 2026
Neeraj Agrawal Forward Deployed Engineer Google Cloud

#Google Cloud#Gemini Enterprise#Cloud Run#Model Context Protocol#Egress Agent Gateway#Private Service Connect#Cloud DNS#Cloud IAM#OAuth 2.0