Hosting

Google-managed remote

Transport

Streamable HTTP

Endpoint

https://run.googleapis.com/mcp

Authentication

Google Cloud authentication: OAuth 2.0 using Application Default Credentials (ADC) in supported Google clients, or a client OAuth ID/secret or bearer token in compatible third-party clients. The principal needs mcp.tools.call plus the underlying product permissions; API key authentication is only available for services that explicitly support it.

Requirements

• A Google Cloud project and access to the target product/resource.
• Enable this MCP service and its underlying Google Cloud API as required by the product guide.
• An MCP client that supports Streamable HTTP.
• An identity with the MCP Tool User role (roles/mcp.toolUser) or equivalent mcp.tools.call permission, plus permissions for the underlying product operations.

Setup steps

1. Choose the correct global or regional endpoint for your data location; this catalog lists the documented endpoint.
2. In the Google Cloud project, enable the MCP service and the underlying product API if the product guide requires it.
3. Authenticate the client with Google Cloud ADC (simplest with Antigravity/Gemini CLI) or configure OAuth 2.0 credentials in a compatible client.
4. Grant the connecting identity roles/mcp.toolUser and only the product IAM roles needed for the intended operations.
5. Add run.googleapis.com to the client as a Streamable HTTP MCP server and complete sign-in.
6. Refresh the client tool list and check that the tools match the product reference; availability may depend on permissions and selected toolset.

Five tools list/get services and deploy from image, archive or inline source. Deployments create/replace services and can incur Cloud Run/Artifact Registry charges; inspect source, environment and IAM. Archive max 250 MiB; inline payload 50 MiB.

• get_service

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

  01
• list_services

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

  02
• deploy_service_from_image

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

  03
• deploy_service_from_archive

  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: 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. Upload the archive to a Google Cloud Storage bucket, preferably in the same region as the service. 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).

  04
• deploy_service_from_file_contents

  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: source_code: Should set to sourceCode.inlinedSource.sources with array of source files, each having filename and content . Size limit: you are subject to total request size limit of 50MiB.

  05

• Deploy actions can create or change billable Cloud Run resources; require explicit confirmation.

• official server catalog

  Official Google Cloud catalog lists this product as an available remote MCP server.

• official setup guide

  Google Cloud describes remote MCP client setup, Streamable HTTP transport, supported authentication options, and ADC setup.

• official authentication guide

  Google documents supported identity types and authorization requirements for Google Cloud MCP calls.

• official source

  Official Google Cloud MCP product reference/guide; checked 2026-10-28.

• official source

  Official Google Cloud MCP product reference/guide; checked 2026-10-28.

Documentation checked 2026-10-28. Connection has not been runtime tested.