Deploy applications to Cloud Run. Connect the official Google Cloud Run MCP server to Claude, ChatGPT, or Cursor through gate — one gateway URL, no config files, security-checked.
Free to start · No credit card · No hosting needed
Pick your client. Copy, paste, done — or let gate handle sign-ins and policies for you.
claude mcp add --transport http google-cloud-run https://run.googleapis.com/mcpRun in your terminal, then restart Claude Code.
Google Cloud Run · https://run.googleapis.com/mcp
Real prompts you can type the moment it's connected — no setup, no docs to read.
“Use “get_service”: Get info about a Cloud Run service, such as its URI and whether the deploy succeeded.”
“Use “list_services”: List Cloud Run services in a given Google Cloud project and region.”
“Use “deploy_service_from_image”: Deploy a container image from Artifact Registry or Docker Hub as a Cloud Run service.”
“Use “deploy_service_from_archive”: Deploy a Cloud Run service directly from a self-contained source code archive (.tar.gz), skipping the container image build step for faster.”
Every server in the gate directory has to pass the same four checks before your AI can touch it. Here's how Google Cloud Run holds up.
Operated by Google Cloud Run (googleapis.com) at its documented MCP endpoint — not a third-party mirror or community re-host.
This server only exposes public data — no account and no credentials are involved when you connect.
gate checks every tool for prompt injection, hidden instructions, data-exfiltration hints, and over-broad permissions before the server is available through your gateway.
If Google Cloud Run adds or changes tools later, gate re-scans and alerts you — before your AI acts on the change.
Add one gateway URL to Claude, ChatGPT, or any MCP client. One-time setup, about two minutes.
Choose Google Cloud Run in the gate directory. No sign-in needed.
Google Cloud Run's tools are live in every AI client you've connected — with rules and logging built in.
Free to start · No credit card · No hosting needed
Fetched live from the official endpoint and re-checked daily by gate — not marketing copy.
get_service — Get info about a Cloud Run service, such as its URI and whether the deploy succeeded.
list_services — List Cloud Run services in a given Google Cloud project and region.
deploy_service_from_image — Deploy a container image from Artifact Registry or Docker Hub as a Cloud Run service.
deploy_service_from_archive — Deploy a Cloud Run service directly from a self-contained source code archive (.tar.gz), skipping the container image build step for faster
deploy_service_from_file_contents — Deploys a Cloud Run service directly from local source files. This method is suitable for scripting languages like Python and Node.js, of wh
https://run.googleapis.com/mcpYes — Google Cloud Run operates its own remote MCP server at run.googleapis.com. gate connects you to that official endpoint and adds security scanning, per-tool access rules, and an activity log on top.
Add gate's gateway URL to your AI client once, then pick Google Cloud Run in the directory. No account or sign-in is needed. From then on, Google Cloud Run's tools are available in every client you've connected to gate.
No. Google Cloud Run runs the server, and gate is fully managed. You just connect one URL — there's nothing to install, deploy, or maintain.
It's the vendor's official endpoint, and gate scans its tools for prompt injection and hidden instructions before it goes live, re-checks it whenever it changes, and lets you allow, block, or require approval for every single tool.
Yes — you can get started with gate for free and connect Google Cloud Run in minutes. No credit card required.
Every server below works through the same gateway URL — connect once, add tools anytime.
Set up Google Cloud Run in: Claude · Claude Code · ChatGPT · Cursor · VS Code
One URL. All MCPs. Full control. Free to start.
Get started free