Google Cloud Run MCP server

• deploy_service_from_archivewrite actionFree

  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_contentswrite actionFree

  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_imagewrite actionFree

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

• get_serviceFree

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

• list_servicesFree

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

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 568ms20/20
• Tool poisoning5 tool descriptions checked15/15
• Auth qualityopen endpoint exposes 3 write-action tools with no auth3/15
• Maintenanceno repository listed3/15
• Maintainer identityno repository or website to verify2/10

Safety score

57/100

higher than 11% of 1,119 Developer tools servers

Tools

5

the typical Developer tools server has 7

Tools that change things

60%

typical: 5%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote Developer tools server answers 100%

Response time

84 ms

faster than 78% of 443 Developer tools servers

Google Cloud Run: common questions

Is Google Cloud Run MCP server safe?

With care: it is graded C, so read the findings first (57/100). Read the Google Cloud Run safety report

How do I install Google Cloud Run?

It runs remotely at run.googleapis.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Google Cloud Run need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Google Cloud Run maintained?

The latest release is v2.0.0.

Is Google Cloud Run up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

What can I use instead of Google Cloud Run?

Servers from other publishers that do the same job: TerraVision MCP server, walkerOS Flow MCP server and Omnara MCP server.

How does Google Cloud Run compare with other Developer tools MCP servers?

safety score 57/100 (higher than 11% of 1,119 Developer tools servers); tools 5 (the typical Developer tools server has 7); tools that change things 60% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.