@google-cloud/cloud-run-mcp
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 0 of 1 tool tried
Contacts while installing and starting: metadata.google.internal, metadata.google.internal.2g0bjc0siemufpke4lmjtmzvyf.ftyx.internal.cloudapp.net, 169.254.169.254:80
What it contacted
metadata.google.internal: the cloud metadata address; cloud SDKs probe it when looking for credentialsmetadata.google.internal.2g0bjc0siemufpke4lmjtmzvyf.ftyx.internal.cloudapp.net: the cloud metadata address; cloud SDKs probe it when looking for credentials169.254.169.254:80: the cloud metadata address; cloud SDKs probe it when looking for credentials
Hosts it looked up or connected to while installing and starting with no input, watched from outside its sandbox. The npm registry is left out. Says nothing about what its tools contact when called.
Starting it
npx -y @google-cloud/cloud-run-mcp@1.12.0
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
1 tool that takes no input and looks read-only was called once with nothing. 0 returned a result.
list_projects | No usable answer replied, but asks for setup: GCP credentials are not available. Please configure your environment using OAuth or `gcloud auth`. |
During the calls it contacted nothing it had not already contacted.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
list_projects
Lists available GCP projects
create_project projectId
Creates a new GCP project and attempts to attach it to the first available billing account. A project ID can be optionally specified; otherwise it will be automatically generated.
list_services project
Lists all Cloud Run services in a given project.
get_service project, region, service
Gets details for a specific Cloud Run service.
get_service_log project, region, service
Gets Logs and Error Messages for a specific Cloud Run service.
deploy_local_folder project, region, service, folderPath
Deploy a local folder to Cloud Run. Takes an absolute folder path from the local filesystem that will be deployed. Use this tool if the entire folder content needs to be deployed.
deploy_file_contents project, region, service, files
Deploy files to Cloud Run by providing their contents directly. Takes an array of file objects containing filename and content. Use this tool if the files only exist in the current chat context.
deploy_container_image project, region, service, imageUrl
Deploys a container image to Cloud Run. Use this tool if the user provides a container image URL.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | Apache-2.0 |
|---|---|
| Needs | not stated |
| Source | github.com/GoogleCloudPlatform/cloud-run-mcp |
| Install scripts | protobufjs declare them. This runner does not run them. |
| Tarball | sha512-EB5Y9ofkSAG+QCXhAvd2md5/m6GQH1glHbI+WmqIgYZlQXZU98wbNJeMR/JxTNxgpXtwTza7Iifuse5Eu6s0tg== |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40google-cloud/cloud-run-mcp)
New version out? Ask for a fresh report.