Google Cloud Run MCP
Capped at 70: no passing tool call yet; the tests add up to 100. Why scores are capped
Test points add up to 100; the score is capped at 70 until a tool call passes. Not a quality or security rating. Methodology
Test points before the cap (100/100)
- Install20/20
- Handshake30/30
- Maintenance25/25
- Docs15/15
- License10/10
Tested npm @google-cloud/cloud-run-mcp 1.12.0 (Apache-2.0; repo GoogleCloudPlatform/cloud-run-mcp). Installed pinned with scripts off (npm --ignore-scripts) and launched: initialize and tools/list over stdio succeeded with no credentials and listed 8 tools (no tool annotations). Real calls: 0 of 3 real function calls passed. Calls need Google Cloud credentials (gcloud auth / ADC). Core tools not tested: 70 cap.
Tool-call test (2026-11-13 UTC, direct MCP stdio client, no LLM): fail. 0 of 3 real function calls passed. Calls need Google Cloud credentials (gcloud auth / ADC). Evidence: local test run, Nov 13, 2026 UTC.
Transport (tested 2026-11-13 UTC): stdio
Token cost (estimate): approx. 969 tokens, cl100k estimate (8 tools, measured 2026-11-13 UTC, version 1.12.0). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.
Permissions: 4 read, 4 write (state-changing), 0 unclassified · Auth: API key · Rate limit: unknown · Pricing unit: unknown
Auth: API key. Rate limit: unknown. Pricing unit: unknown.
create_project— write (state-changing)deploy_container_image— write (state-changing)deploy_file_contents— write (state-changing)deploy_local_folder— write (state-changing)get_service— readget_service_log— readlist_projects— readlist_services— read
listing-flags calls_need_key or auth_kind
Score 70/100 · Tools 8 · Token cost approx. 969 tokens · Compare · Last tested 2026-11-13 UTC · Version tested 1.12.0 · Package @google-cloud/cloud-run-mcp · Repo GoogleCloudPlatform/cloud-run-mcp
Summary: Google Cloud Run MCP completed an MCP handshake without credentials and exposed 8 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 8
- Context cost
- approx. 969 tokens, cl100k estimate (8 tools, measured 2026-11-13 UTC, version 1.12.0; an estimate) ranking · add up your servers' context cost
- API key
- Connects without a key; tool calls need one
- Tested
- 2026-11-13 UTC
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | npm install @google-cloud/cloud-run-mcp (Node 20, Linux) succeeded in 5s. |
| handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 8 tools listed in 5.9s. |
| maintenance | pass | 25 | Repo pushed 0 days before test; 639 GitHub stars. |
| docs | pass | 15 | README over 3,000 chars; install instructions present; mcpServers config example present. Check of the package's own README (README shipped in npm package). |
| license | pass | 10 | Apache-2.0 (OSI-approved). |
Local-model readiness
Token cost (estimate): approx. 969 tokens, cl100k estimate for 8 tools · about 12% of an 8k context. This is an estimate from our testing (counted with cl100k_base).
Small-model friendly (schema heuristic, not a model result): unknown.
Not tested
Small-model task runs: Not yet tested.
What we tested and what we didn't
Tested on 2026-11-13 UTC
- Install from the registry
- We connected with no credentials and asked for its tool list: it listed 8 tools (Method details: MCP
initializethentools/list) - Maintenance signals (last push, archived/deprecated status)
- Docs (README length, install and config example)
- License (OSI-approved or not)
- Token cost (estimate)
Not tested
- Security: not audited (no code review, no permission or data-flow analysis)
- Real tasks (no functional task runs yet)
- Behaviour with real credentials or a real account
- Performance, rate limits or load
- Correctness of results beyond the listed tasks
Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.
Known security issues
Not yet checked.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
Baseline recorded from the 2026-11-13 UTC test run; changes appear after the next test.
Snapshot hash (fingerprint of the tool list)
822b6433043a: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "@google-cloud/cloud-run-mcp",
"version": "1.12.0",
"registry": "npm",
"status": "working",
"tested": "2026-11-13",
"tools_count": 8,
"deprecated": false,
"archived": false,
"tests": {
"install": [
"pass",
20,
"`npm install @google-cloud/cloud-run-mcp` (Node 20, Linux) succeeded in 5s."
],
"handshake": [
"pass",
30,
"MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 8 tools listed in 5.9s."
],
"maintenance": [
"pass",
25,
"Repo pushed 0 days before test; 639 GitHub stars."
],
"docs": [
"pass",
15,
"README over 3,000 chars; install instructions present; `mcpServers` config example present. Check of the package's own README (README shipped in npm package)."
],
"license": [
"pass",
10,
"Apache-2.0 (OSI-approved)."
]
}
}Install
npx -y @google-cloud/cloud-run-mcp
Pin the version we tested
npx -y @google-cloud/cloud-run-mcp@1.12.0
tested 2026-11-13 UTC. Newer versions may differ and were not tested by us.
{
"mcpServers": {
"google-cloud-run-mcp": {
"command": "npx",
"args": [
"-y",
"@google-cloud/cloud-run-mcp@1.12.0"
]
}
}
}Tools listed
list_projects, create_project, list_services, get_service, get_service_log, deploy_local_folder, deploy_file_contents, deploy_container_image
Quick config
{
"mcpServers": {
"google-cloud-run-mcp": {
"command": "npx",
"args": [
"-y",
"@google-cloud/cloud-run-mcp"
]
}
}
}Add to config Opens the config generator with this server selected.
Setup
- Install. Run
npm install @google-cloud/cloud-run-mcp(Node 20). This is the exact command we ran on 2026-11-13 UTC. - Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools (8 in our test).
{
"mcpServers": {
"google-cloud-run-mcp": {
"command": "npx",
"args": [
"-y",
"@google-cloud/cloud-run-mcp"
]
}
}
}Test history
- 2026-11-13 UTC: New
FAQ
Is Google Cloud Run MCP deprecated?
No. @google-cloud/cloud-run-mcp was not deprecated or archived when we last tested it on 2026-11-13 UTC.
What replaces Google Cloud Run MCP?
Nothing; Google Cloud Run MCP is not deprecated as of 2026-11-13 UTC.
Does Google Cloud Run MCP need an API key?
It connects and lists 8 tools without a key, but its tool calls need one.
Embed the badge
Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.