Create

Sign in to ReadmeX

or

How we handle your data: Privacy Policy

ReadmeX

Your AI reading companion

What would you like to catch up on?

Pick a briefing, or ask your own question.

Your community and people briefings stay personal to you.

Story

Google details private MCP connectivity for Gemini Enterprise

AI summary

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.

In-depth insight

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

header_image_1600x900

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

Original · 7 min readRead the original
Group chat

No comments yet. Start the conversation.