Google Cloud Run MCP Server

by googleapis-run Your server? Claim it

answering

Google Cloud Run is answering right now. Last checked 1 min ago. It exposes 5 tools.

Deploy applications to Cloud Run

Uptime history 51 days of history

51 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

266 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 22

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 3 September 2026. No other catalogue keeps this.

4 Sep 2 tools changed the parameters they ask for6 times that day deploy_service_from_archive, deploy_service_from_file_contents

3 Sep 2 tools changed the parameters they ask for16 times that day deploy_service_from_archive, deploy_service_from_file_contents

and 18 more, back to 3 September 2026

Nothing serious here today

Today is the operative word: we check Google Cloud Run every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp --transport http https://run.googleapis.com/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://run.googleapis.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.mcp]
url = "https://run.googleapis.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://run.googleapis.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://run.googleapis.com/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

deploy

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 deployment. The archive must include all dependencies: - For compiled languages (Go, Java), include pre-compiled binaries. - For scripting languages (Python, Node.js), include pre-installed libraries (e.g., vendor/, node_modules/). Deployment steps: 1. Package source code and dependencies into a .tar.gz archive (max 250MiB). It's recommended to create archive from the root of the application's source directory. 2. Upload the archive to a Google Cloud Storage bucket, preferably in the same region as the service. 3. Deploy to Cloud Run using this tool, specifying: - source_code: Google Cloud Storage object path to the archive (e.g., gs://bucket/object). - command: Command to start the application. - base_image_uri: Base image for the container (e.g., go124, nodejs24, python314). See https://docs.cloud.google.com/run/docs/configuring/services/runtime-base-images for options. The runtime picked should match the local environment. - args: (Optional) Arguments for the command. - env: (Optional) Environment variables (e.g., name: `PYTHONPATH`, value: `./vendor`). - ports: (Optional) Container ports to expose (defaults to 8080).

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 which the source code can be embedded in the request. This is ideal for quick tests and development feedback loops. You must include all necessary dependencies within the source files because it skips the build step for faster deployment. **Key Requirements:** 1. source_code: Should set to sourceCode.inlinedSource.sources with array of source files, each having `filename` and `content`. 2. Size limit: you are subject to total request size limit of 50MiB.

deploy_service_from_image

Deploy a container image from Artifact Registry or Docker Hub as a Cloud Run service.

service

get_service

Get info about a Cloud Run service, such as its URI and whether the deploy succeeded.

services

list_services

List Cloud Run services in a given Google Cloud project and region.

Endpoints

URL	Transport	State	Latency	Checked
https://run.googleapis.com/mcp	streamable-http	answering	246 ms	1 min ago

Alternatives to Google Cloud Run

same job, measured the same way

Patents MCP

by mrfentmen

Search US patents and patent applications from Google Patents. No key required.

local only

Googleapis

by googleapis-mapstools

Ground your AI applications with trusted geospatial data from Google Maps.

5 tools answering

Bim

by makata

Design-review threads, comments, reactions and deployments from Bim. Sign in with Google.

answering

Remote Filesystem

by pulsemcp

MCP server for remote filesystem operations on cloud storage (Google Cloud Storage).

51 installs/wk local only

Google Apps Script MCP

by a1-x-tech

MCP server for the Google Apps Script API: projects, code, versions, deployments and executions.

183 installs/wk local only

Googleapis

by googleapis-developerknowledge

Provides access to Google's public developer documentation.

3 tools answering

Googleapis

by googleapis-sqladmin

Create, manage, and query your Google Cloud SQL resources.

15 tools answering

Google Docs

by domdomegg

Allow AI systems to read and edit Google Docs.

36 installs/wk local only

Google Cloud Run — questions

Answers built from our own checks of this server.

What can Google Cloud Run do?

It exposes 5 tools, read directly from the server on our last check. Among them: deploy_service_from_archive, deploy_service_from_file_contents, deploy_service_from_image, get_service, list_services. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Google Cloud Run working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 266 ms. The bar chart above shows every period we have measured.

How do I connect Google Cloud Run?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Google Cloud Run need an API key?

No. Google Cloud Run completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Google Cloud Run?

It answers our handshake in 266 ms on average, which is faster than 58% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.