Google Cloud Run MCP server

Endpoint: https://run.googleapis.com/mcp · Authentication: Sign in with OAuth

Lists and inspects Cloud Run services and deploys services from container images or source archives. Requires Google Cloud credentials through OAuth.

How do I authenticate?

Add the endpoint in your client, start Connect or Sign in, approve the requested scopes, and return to the client. OAuth discovery finds the authorization server; client registration requirements vary by provider. Follow the provider guidance and client setup below.

Authentication and connection guide

Connection specification

Remote endpoint
https://run.googleapis.com/mcp
Browser access
Not yet measured
Declared MCP transport
Streamable HTTP
Live-validated MCP transport
Streamable HTTP — Observed by the latest catalog validation
Declared authentication
OAuth 2.1
Detected authentication
OAuth 2.1 detected or retained from publisher evidence
Protocol lifecycle
Stateful MCP · 2025-11-25
Authorization server
https://accounts.google.com/
Category
Cloud

Product documentation · Official listing documentation

Provider guidance

  • Initialization and tool listing succeeded without credentials in the 2026-10-20 audit; tool calls require Google Cloud credentials. Google OAuth clients are pre-registered in a Google Cloud project; the server does not advertise Dynamic Client Registration.

More Cloud MCP servers · Browse all MCP servers · Test this endpoint in the MCP Playground

Authorization setup

Registration requirements not verified

The OAuth authorization and app-registration requirements for this exact endpoint have not been verified. A compatible client will request authorization, but follow the publisher documentation and do not guess client credentials or callbacks.

Publisher evidence reviewed .

Publisher documentation

Connect it

Live-validated endpoint: https://run.googleapis.com/mcp · Streamable HTTP. Registration requirements not verified: The OAuth authorization and app-registration requirements for this exact endpoint have not been verified. A compatible client will request authorization, but follow the publisher documentation and do not guess client credentials or callbacks.

Agent prompt for Claude Code or Codex
Add the Google Cloud Run MCP server to my MCP client configuration and verify that it works.

What it is: Lists and inspects Cloud Run services and deploys services from container images or source archives. Requires Google Cloud credentials through OAuth.
Server URL: https://run.googleapis.com/mcp
Transport: Streamable HTTP (remote MCP server, no local install).
Authentication: OAuth 2.1. Registration requirements not verified: The OAuth authorization and app-registration requirements for this exact endpoint have not been verified. A compatible client will request authorization, but follow the publisher documentation and do not guess client credentials or callbacks.
Tools (5, as last observed by mcptest): deploy_service_from_archive, deploy_service_from_file_contents, deploy_service_from_image, get_service, list_services.
Reference: https://mcptest.io/servers/google-cloud-run/

Steps:
1. Work out which MCP client I use (Claude Code, Codex, Cursor, VS Code or another) and add the server under the name "google-cloud-run" in that client's MCP configuration, user scope unless I ask otherwise.
   Claude Code: claude mcp add --transport http --scope user 'google-cloud-run' 'https://run.googleapis.com/mcp'
   Other clients: use the setup for that client on the reference page.
2. Never write a credential value into a file that could be committed; reference an environment variable or the client's secret store, and ask me for any value you need.
3. Verify: connect to the server and call tools/list. Confirm the tools above are listed, and report any sign-in step I still have to complete.
MCP client

Claude Code setup

Run in a terminal. This user-scoped entry is available across projects.

claude mcp add --transport http --scope user 'google-cloud-run' 'https://run.googleapis.com/mcp'
  • After adding the server, open Claude Code, run /mcp, select the server, and follow the browser flow to authenticate.

Codex CLI setup

Run in a terminal; Codex stores the entry in ~/.codex/config.toml.

codex mcp add 'google-cloud-run' --url 'https://run.googleapis.com/mcp'
codex mcp login 'google-cloud-run'

Cursor setup

Add to .cursor/mcp.json for this project, or ~/.cursor/mcp.json for all projects.

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

VS Code setup

Add to .vscode/mcp.json, or run “MCP: Open User Configuration” for a private user-level entry.

{
  "servers": {
    "google-cloud-run": {
      "type": "http",
      "url": "https://run.googleapis.com/mcp"
    }
  }
}

Claude setup

Add the endpoint above in Claude:

  • Customize > Connectors > Add custom connector
  • Team/Enterprise: Organization settings > Connectors > Add > Custom > Web

Claude Desktop setup

Add the endpoint above in Claude Desktop:

  • Remote: Customize > Connectors (same as claude.ai)
  • Local: Settings > Developer > Edit Config, or Settings > Extensions for .mcpb files
  • ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), local servers only

ChatGPT setup

Add the endpoint above in ChatGPT:

  • ChatGPT web: Plugins > Add custom MCP server, then configure authentication and accept the risk warning

Windsurf setup

Add the endpoint above in Windsurf:

  • ~/.config/devin/mcp_config.json (%APPDATA%\devin\mcp_config.json on Windows), serverUrl or url
  • Cascade panel > ... > MCPs > Open MCP config file

Gemini CLI setup

Add the endpoint above in Gemini CLI:

  • gemini mcp add --transport http <name> <url>
  • ~/.gemini/settings.json (user) or .gemini/settings.json (project), mcpServers

MCP SDK setup

Add the endpoint above in MCP SDK:

  • Programmatic: new Client(...).connect(new StreamableHTTPClientTransport(url))

Notes for every client

  • Publisher evidence (reviewed 2026-10-20): https://docs.cloud.google.com/run/docs/use-cloud-run-mcp
  • Provider guidance: Initialization and tool listing succeeded without credentials in the 2026-10-20 audit; tool calls require Google Cloud credentials. Google OAuth clients are pre-registered in a Google Cloud project; the server does not advertise Dynamic Client Registration.

Client compatibility

ClientStatusWhy
Claude CodeSupportedClaude Code supports Streamable HTTP servers and OAuth sign-in.
CodexPartialCodex CLI ignores prompts: The server can still connect, but Codex CLI does not consume the advertised prompts capability.
CursorSupportedCursor supports Streamable HTTP servers and OAuth sign-in.
VS CodeSupportedVS Code supports Streamable HTTP servers and OAuth sign-in.
ClaudeSupportedClaude supports Streamable HTTP servers and OAuth sign-in.
Claude DesktopSupportedClaude Desktop supports Streamable HTTP servers and OAuth sign-in.
ChatGPTPartialChatGPT ignores prompts: The server can still connect, but ChatGPT does not consume the advertised prompts capability. Stateful routing needs operational care: ChatGPT can preserve MCP sessions, but the deployment must route a session consistently and retain its state.
WindsurfPartialWindsurf's documentation does not state support for OAuth sign-in.
Gemini CLISupportedGemini CLI supports Streamable HTTP servers and OAuth sign-in.
MCP SDKSupportedMCP SDK supports Streamable HTTP servers and OAuth sign-in.

Computed from this server's validated transport, protocol and authentication against documented client support. Checks the catalog has not observed are not counted.

Similar servers

  • Cloudflare — Remote MCP server for Cloudflare Workers, D1, R2, DNS, and account APIs. OAuth 2.1
  • Vercel — Vercel's remote MCP server for inspecting and managing projects, deployments, logs, and platform resources. OAuth 2.1
  • Cloudflare Workers Bindings — Manages the storage, AI, and compute primitives that Workers bind to, such as KV, R2, and D1, in a Cloudflare account. Requires Cloudflare OAuth. OAuth 2.1
  • Cloudflare Workers Builds — Lists Workers Builds and reads their status and logs for Workers connected to Git. Requires Cloudflare OAuth. OAuth 2.1
  • Cloudflare Browser Run — Fetches web pages through Cloudflare Browser Rendering and returns HTML, Markdown, or screenshots. Requires Cloudflare OAuth. OAuth 2.1
  • Cloudflare Containers — Spins up a sandboxed container development environment for running code. Requires Cloudflare OAuth. OAuth 2.1

Guides for this server

Watch this server for breaking changes

Share and embed

Maintain Google Cloud Run? Embed this badge in your README. It follows the latest catalog validation result and links to this server profile.

mcptest.io: ready

Latest validation evidence

Validation status
Online when last tested
Validation checked at
Oct 26, 2026 at 11:06 AM
Validation detail
Negotiated stateful MCP 2025-11-25 at https://run.googleapis.com/mcp; detected transport streamable-http; authentication oauth

Tool inventory

What the catalog validator observed on at https://run.googleapis.com/mcp without credentials. The live server may have changed since; connect in the Playground for the current list.

Tools provided by Google Cloud Run 5

Some details were sanitized for public display.

  • deploy_service_from_archiveoutputSchema declared

    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 Stora

    Input service: any
    • service: anyrequired

      Required. The service to deploy.

  • deploy_service_from_file_contentsoutputSchema declared

    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.

    Input service: any
    • service: anyrequired

      Required. The service to deploy.

  • deploy_service_from_imageoutputSchema declared

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

    Input service: any
    • service: anyrequired

      Required. The service to deploy.

  • get_serviceoutputSchema declared

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

    Input name: string, project: string, region: string
    • name: stringrequired

      Required. The short name of the Service.

    • project: stringrequired

      Required. The project ID or project number to get the Service from.

    • region: stringrequired

      Required. The region to get the Service from.

  • list_servicesoutputSchema declared

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

    Input project: string, region: string
    • project: stringrequired

      Required. The project ID or project number to list the Services from.

    • region: stringrequired

      Required. The region to list the Services from.

Prompts 1

  • deploy

    Deploys the current working directory to Cloud Run.

    Arguments name?: any, project: any, region: any
    • name?: anyoptional

      Name of the Cloud Run service to deploy to. Defaults to the name of the current directory.

    • project: anyrequired

      Google Cloud project ID.

    • region: anyrequired

      Region where the services are located.