Connect Google Cloud Run MCP to your AI agents, securely.
One secured endpoint for every Google Cloud Run call your AI agents make, scoped per user, inspected, and logged.Try Google Cloud Run MCP now
What your agents can ask once Google Cloud Run MCP is connected.
“List the Cloud Run services in this project”
“Deploy this container image as a new service”
“What is the URL of this service?”
“Deploy a new revision of this service”
“Deploy these source files to Cloud Run”
“Which region is this service running in?”
Select the tools your AI agents can call
5 tools from the Google Cloud Run MCP schema.
Showing 5 tools
What Google Cloud Run MCP exposes
Google Cloud Run MCP groups its 5 tools into 1 categories, each with a suggested starting policy.
| Category | Covers | Access | Suggested policy |
|---|---|---|---|
| Services | Service listing, details, creation, updates and deletion | Read / Write | Approve deployments; require approval for deletes |
Connect Google Cloud Run MCP to your AI agent
Four steps, under ten minutes.
- 01
Sign in to NeuralTrust
Open the NeuralTrust platform, sign in and go to Getting started, then Connect your tools.
- 02
Choose your agent
When asked which agent you use, pick Claude Code, Codex, Cursor, Windsurf, Copilot or your own code.
- 03
Connect Google Cloud Run
Find Google Cloud Run in the tool list and connect it.
- 04
Connect your agent
Follow the steps on screen to add the config to your agent, then send the test prompt.
Permissions down to the single tool
You do not allow Google Cloud Run MCP or block it. You allow the exact tools each agent can call, one by one.
| Google Cloud Run MCP | 5 TOOLS AVAILABLE |
|---|---|
| Code review agent | 4 tools, read only |
| Issue triage bot | 9 tools |
| Platform team assistant | all 5 tools |
- Tool by toolConnecting the server is not the unit of access. Each tool is granted on its own.
- Default denyA tool you have not enabled is never exposed to the agent.
- Approval on writesTools that change or delete things can require a human to confirm.
Is Google Cloud Run MCP secure?
One endpoint instead of raw credentials. Every call is checked against policy and logged.
| AI agentsConnect through your MCP client configuration. | NeuralTrustApply controls based on your configuration. | Google Cloud Run MCP5 documented tools. |
|---|---|---|
| Coding assistants | Connection & credentialsper user | Services5 tools |
| Internal copilots | Tool access policiesdeny by default | |
| Workflow automations | Request & response inspectioninline | |
| Compatible MCP clients | Activity monitoringalerts and logs |
Use Google Cloud Run MCP with any AI agent framework
Setup guides for the tools your team already uses.
- Claude CodeSetup guide
- CursorSetup guide
- CodexSetup guide
- WindsurfSetup guide
- Gemini CLISetup guide
- Google AntigravitySetup guide
- GitHub CopilotSetup guide
- Claude EnterpriseSetup guide
- Microsoft Copilot StudioSetup guide
- Open WebUISetup guide
- LangChainSetup guide
- HaystackSetup guide
- Strands AgentsSetup guide
- Vercel AI SDKSetup guide
- n8nSetup guide
Common questions about running Google Cloud Run MCP through TrustGate.
Other MCP servers
More servers from the catalog.
Google Cloud GKE
Securely connect your AI agents to Google Cloud GKE through TrustGate: clusters, node pools, operations and Kubernetes resources, scoped per agent and logged.
25 toolsViewGoogle Compute Engine
Securely connect your AI agents to Google Compute Engine through TrustGate: instances, instance groups and templates, disks, snapshots, images, reservations and commitments, scoped per agent and logged.
29 toolsViewGoogle Cloud Monitoring
Securely connect your AI agents to Google Cloud Monitoring through TrustGate: time series, metric descriptors, alert policies, alerts and dashboards, scoped per agent and logged.
9 toolsView
Connect Google Cloud Run MCP instantly
Pick the tools, point your agent at TrustGate, and Google Cloud Run MCP is live: scoped, inspected, logged.