Google Cloud Run
warningsrun.googleapis.com
Deploy applications to Cloud Run
https://run.googleapis.com/mcpOAuthMCP 2026-07-28vESFlast checked 9 Oct 2026spoke MCP on 100% of 90 checks (30 days)initialize in 124 msWill my client connect?
Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.
✓Claude CodeConnects with setup
Neither RFC 7591 registration nor a Client ID Metadata Document is advertised, so register a client with the issuer yourself and give Claude Code the client ID.
claude mcp add --transport http --client-id <your-client-id> --client-secret --callback-port 8080 google-cloud-run https://run.googleapis.com/mcpClaude Code docs · read on 2026-08-30
✓Claude (claude.ai & Desktop)Connects with setup
Neither RFC 7591 registration nor a Client ID Metadata Document is advertised, so register a client with the issuer yourself and give Claude (claude.ai & Desktop) the client ID.
Settings → Connectors → Add custom connector, then paste https://run.googleapis.com/mcp. Under Advanced settings, enter the OAuth Client ID and Secret the issuer gave you.
Claude (claude.ai & Desktop) docs · read on 2026-08-30
✕ChatGPTNot supported
Registering a client by hand is not a flow ChatGPT documents, and this server advertises none that it does.
ChatGPT docs · read on 2026-08-30
✓CursorConnects with setup
Neither RFC 7591 registration nor a Client ID Metadata Document is advertised, so register a client with the issuer yourself and give Cursor the client ID.
{
"mcpServers": {
"google-cloud-run": {
"url": "https://run.googleapis.com/mcp"
}
}
}Cursor docs · read on 2026-08-30
✓VS Code (Copilot)Connects with setup
Neither RFC 7591 registration nor a Client ID Metadata Document is advertised, so register a client with the issuer yourself and give VS Code (Copilot) the client ID.
{
"servers": {
"google-cloud-run": {
"oauth": {
"clientId": "<your-client-id>"
},
"type": "http",
"url": "https://run.googleapis.com/mcp"
}
}
}VS Code (Copilot) docs · read on 2026-08-30
How to authenticate
Checked against the endpoint by our probe on 9 Oct 2026. These are the capabilities the server advertises, not a prediction about any particular client.
| Scheme | OAuth |
|---|---|
| Issuer | https://accounts.google.com |
| Dynamic client registration | ✕Not advertised A client that cannot register itself needs credentials issued out of band before it can begin the flow. |
| Client ID Metadata Document | ✕Not advertised |
| PKCE | ✓plain, S256 |
| Grant types | authorization_code, refresh_token, urn:ietf:params:oauth:grant-type:device_code, urn:ietf:params:oauth:grant-type:jwt-bearer |
| Protected-resource metadata | ✓Published (RFC 9728) |
| Anonymous access | Handshake succeeds; 5 tools listable |
What the probe found
A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.
The server exposes a public surface before authorization: get_service, list_services, deploy_service_from_image, deploy_service_from_archive, deploy_service_from_file_contents.
Tools
Contract history
Instructions rewritten: get_service, list_services. The description an agent follows changed; the callable contract may not have.
Watch this server
Save its public contract as a baseline and manage breaking-change email alerts.
Set up a watchOwn this server?
Sign in to claim this listing by proving control of its host.
Status badge
Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.
[](https://mcpi.app/servers/google-cloud-run)