Content Deep Dive

How to securely connect internal Cloud Run MCP servers to Gemini Enterprise

Blog post from Google Cloud

Post Details
Company
Date Published
Author
Neeraj Agrawal
Word Count
1,379
Company Posts That Month
22
Language
English
Hacker News Points
-
Post removed?
No
Summary

Gemini Enterprise can connect securely to internal Model Context Protocol (MCP) servers hosted on Cloud Run by combining an Egress Agent Gateway, Private Service Connect (PSC) Network Attachment, and carefully scoped Private Cloud DNS. This setup addresses three production concerns: blocking public access to Cloud Run, verifying both the Gemini Enterprise service and the signed-in user, and avoiding DNS conflicts in Shared VPCs. Traffic enters the private VPC through the gateway and reaches Cloud Run using either Subnet Private Google Access or a global PSC endpoint for Google APIs; an exact-hostname DNS zone directs only the MCP server’s traffic privately while leaving other Cloud Run services unaffected. For authentication, Cloud Run IAM checks a Google-signed service token, while the MCP application validates the user’s OAuth 2.0 bearer token and applies user-level permissions. A companion GitHub repository provides a Python reference server, deployment scripts, configuration instructions, and logging checks for testing the private connection.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
MCP 23 9,757 959 203 -18%
Serverless 7 833 236 92 -40%
AI Agents 1 6,233 1,230 245 -11%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.