MCP server de Cloud Run
Commit 14 nov 2026Despliega aplicaciones y archivos en Google Cloud Run y permite listar servicios, proyectos y logs de servicio.
También conocido como GoogleCloudPlatform/cloud-run-mcp, @google-cloud/cloud-run-mcp
- Stars
- 639
- Herramientas
- 8
- Descargas, 30 días
- 38.853
- Última versión
- —
- Último commit
- 14 nov 2026
- Licencia
- Apache-2.0
¿Qué es Cloud Run MCP?
Despliega aplicaciones y archivos en Google Cloud Run y permite listar servicios, proyectos y logs de servicio. Expone 8 herramientas, como list_projects, create_project, list_services.
Resumen generado a partir del README del proyecto
Acerca del MCP server de Cloud Run
Este servidor permite a los desarrolladores que utilizan Google Cloud Platform desplegar aplicaciones y gestionar servicios en la nube a través de agentes de IA. Permite interactuar con Cloud Run mediante clientes compatibles con MCP como Claude Desktop, Cursor o Windsurf. Al conectarte a tu cuenta de Google Cloud usando el Google Cloud SDK, puedes usar lenguaje natural para gestionar tu infraestructura.
El servidor proporciona herramientas específicas para diversas tareas, como desplegar el contenido de un archivo con deploy-file-contents o gestionar directorios locales con deploy-local-folder. También incluye capacidades para listar servicios, obtener detalles específicos de un servicio y recuperar logs o mensajes de error a través de get-service-log. Para quienes trabajan localmente, incluso puede listar los proyectos disponibles o crear nuevos.
Puedes ejecutarlo como un servidor local usando Node.js o Docker, o alojarlo de forma remota en el propio Cloud Run. Las configuraciones remotas requieren autenticación IAM u OAuth 2.0 para garantizar el acceso seguro a tus recursos en la nube. La configuración se gestiona mediante variables de entorno como GOOGLE_CLOUD_PROJECT y GOOGLE_CLOUD_REGION para definir tus objetivos de despliegue predeterminados.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Cómo instalar Cloud Run MCP
Formatos verificados el 10 nov 2026Añadir a CursorAñadir a GooseInstalar Cloud Run MCP en Claude Code
$ claude mcp add cloud-run-mcp -- npx -y @google-cloud/cloud-run-mcpInstalar Cloud Run MCP en Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"cloud-run-mcp": {
"command": "npx",
"args": [
"-y",
"@google-cloud/cloud-run-mcp"
]
}
}
}Instalar Cloud Run MCP en VS Code
.vscode/mcp.json
{
"servers": {
"cloud-run-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@google-cloud/cloud-run-mcp"
]
}
}
}Instalar Cloud Run MCP en VS Code CLI
$ code --add-mcp '{"name":"cloud-run-mcp","type":"stdio","command":"npx","args":["-y","@google-cloud/cloud-run-mcp"]}'Instalar Cloud Run MCP en Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"cloud-run-mcp": {
"command": "npx",
"args": [
"-y",
"@google-cloud/cloud-run-mcp"
]
}
}
}Instalar Cloud Run MCP en Codex
$ codex mcp add cloud-run-mcp -- npx -y @google-cloud/cloud-run-mcpInstalar Cloud Run MCP en Codex config.toml
~/.codex/config.toml
[mcp_servers.cloud-run-mcp] command = "npx" args = ["-y", "@google-cloud/cloud-run-mcp"]
Instalar Cloud Run MCP en Gemini CLI
$ gemini mcp add -s user cloud-run-mcp npx -- -y @google-cloud/cloud-run-mcpInstalar Cloud Run MCP en Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"cloud-run-mcp": {
"command": "npx",
"args": [
"-y",
"@google-cloud/cloud-run-mcp"
]
}
}
}Iniciado por HostedMCP el 16 nov 2026
Ejecutamos este comando para @google-cloud/cloud-run-mcp 1.12.0 en un contenedor aislado sin red ni claves. Respondió y listó 8 herramientas.
Herramientas de Cloud Run MCP 8
Leído del servidor con tools/listlist_projectsLists available GCP projects
create_projectCreates 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_servicesLists all Cloud Run services in a given project.
get_serviceGets details for a specific Cloud Run service.
get_service_logGets Logs and Error Messages for a specific Cloud Run service.
deploy_local_folderDeploy 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_contentsDeploy 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_imageDeploys a container image to Cloud Run. Use this tool if the user provides a container image URL.
| list_projects | Lists available GCP projects | |
| create_project | 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 | Lists all Cloud Run services in a given project. | |
| get_service | Gets details for a specific Cloud Run service. | |
| get_service_log | Gets Logs and Error Messages for a specific Cloud Run service. | |
| deploy_local_folder | 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 | 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 | Deploys a container image to Cloud Run. Use this tool if the user provides a container image URL. |
Configuración
DEFAULT_SERVICE_NAMEGOOGLE_APPLICATION_CREDENTIALSGOOGLE_CLOUD_PROJECTGOOGLE_CLOUD_REGION
| Nombre | Descripción | Tipo |
|---|---|---|
| DEFAULT_SERVICE_NAME | — | |
| GOOGLE_APPLICATION_CREDENTIALS | — | |
| GOOGLE_CLOUD_PROJECT | — | |
| GOOGLE_CLOUD_REGION | — |
Verificaciones automáticas
Ejecutado 16 nov 2026Informe completo →Aún no verificado. Un servidor necesita una puntuación de 80, ningún hallazgo grave y suficientes datos para que podamos revisarlo. Cómo funcionan las verificaciones · Qué corregir para obtener más puntos
- Repositorio de origen vinculado y accesiblegooglecloudplatform/cloud-run-mcp is public and reachablegithub.com/googlecloudplatform/cloud-run-mcp ↗Aprobado
- El paquete indica este repositorio como su origen@google-cloud/cloud-run-mcp names googlecloudplatform/cloud-run-mcp as sourcenpmjs.com/package/@google-cloud/cloud-run-mcp ↗Aprobado
- Procedencia de la compilación (atestación de Sigstore)No build attestation published for this releaseNo verificado
- Licencia de código abierto (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Aprobado
- Commit o lanzamiento en el último añoLast commit or release 2026-11-14github.com/googlecloudplatform/cloud-run-mcp ↗Aprobado
- OpenSSF ScorecardNo verificado
- El nombre del paquete no es similar a un paquete popularNo popular package one edit away from @google-cloud/cloud-run-mcpAprobado
- No hay avisos críticos en el paquete ni en sus dependenciasNo verificado
- Sin instrucciones ocultas para el modelo8 tool descriptions and the README read; no override phrases, credential paths or hidden charactersAprobado
- Las herramientas destructivas están etiquetadasNo tool named like delete, drop or execAprobado
- El endpoint remoto responde al handshake de MCPNo verificado
README
Ver en GitHubCloud Run MCP server and Gemini CLI extension
Enable MCP-compatible AI agents to deploy apps to Cloud Run.
"mcpServers":{
"cloud-run": {
"command": "npx",
"args": ["-y", "@google-cloud/cloud-run-mcp"]
}
}
Deploy from Gemini CLI and other AI-powered CLI agents:
Deploy from AI-powered IDEs:
Deploy from AI assistant apps:
Deploy from agent SDKs, like the Google Gen AI SDK or Agent Development Kit.
[!NOTE]
This is the repository of an MCP server to deploy code to Cloud Run, to learn how to host MCP servers on Cloud Run, visit the Cloud Run documentation.
Tools
-
deploy-file-contents: Deploys files to Cloud Run by providing their contents directly. -
list-services: Lists Cloud Run services in a given project and region. -
get-service: Gets details for a specific Cloud Run service. -
get-service-log: Gets Logs and Error Messages for a specific Cloud Run service. -
deploy-local-folder*: Deploys a local folder to a Google Cloud Run service. -
list-projects*: Lists available GCP projects. -
create-project*: Creates a new GCP project and attach it to the first available billing account. A project ID can be optionally specified.
* only available when running locally
Prompts
Prompts are natural language commands that can be used to perform common tasks. They are shortcuts for executing tool calls with pre-filled arguments.
deploy: Deploys the current working directory to Cloud Run. If a service name is not provided, it will use theDEFAULT_SERVICE_NAMEenvironment variable, or the name of the current working directory.logs: Gets the logs for a Cloud Run service. If a service name is not provided, it will use theDEFAULT_SERVICE_NAMEenvironment variable, or the name of the current working directory.
Environment Variables
The Cloud Run MCP server can be configured using the following environment variables:
| Variable | Description |
|---|---|
GOOGLE_CLOUD_PROJECT |
The default project ID to use for Cloud Run services. |
GOOGLE_CLOUD_REGION |
The default region to use for Cloud Run services. |
DEFAULT_SERVICE_NAME |
The default service name to use for Cloud Run services. |
SKIP_IAM_CHECK |
Controls whether to check for IAM permissions for a Cloud Run service. Set to false to enable checks. This is true by default which is a recommended way to make the service public. |
ENABLE_HOST_VALIDATION |
Prevents DNS Rebinding attacks by validating the Host header. This is disabled by default. |
ALLOWED_HOSTS |
Comma-separated list of allowed Host headers (if host validation is enabled). The default value is localhost,127.0.0.1,::1. |
OAUTH_ENABLED |
Enables OAuth 2.0 Bearer token verification for incoming HTTP/SSE requests when set to true. Disabled by default. |
GOOGLE_OAUTH_AUDIENCE |
Expected OAuth 2.0 token audience (typically your OAuth Client ID). Required when OAUTH_ENABLED=true. |
Use as a Gemini CLI extension
To install this as a Gemini CLI extension, run the following command:
-
Install the extension:
gemini extensions install https://github.com/GoogleCloudPlatform/cloud-run-mcp -
Log in to your Google Cloud account using the command:
gcloud auth login -
Set up application credentials using the command:
gcloud auth application-default login
Use in MCP Clients
Learn how to configure your MCP client
Most MCP clients require a configuration file to be created or modified to add the MCP server.
The configuration file syntax can be different across clients. Please refer to the following links for the latest expected syntax:
Once you have identified how to configure your MCP client, select one of these two options to set up the MCP server. We recommend setting up as a local MCP server using Node.js.
Set up as local MCP server
Run the Cloud Run MCP server on your local machine using local Google Cloud credentials. This is best if you are using an AI-assisted IDE (e.g. Cursor) or a desktop AI application (e.g. Claude).
-
Install the Google Cloud SDK and authenticate with your Google account.
-
Log in to your Google Cloud account using the command:
gcloud auth login -
Set up application credentials using the command:
gcloud auth application-default login
Then configure the MCP server using either Node.js or Docker:
Using Node.js
-
Install Node.js (LTS version recommended).
-
Update the MCP configuration file of your MCP client with the following:
"cloud-run": { "command": "npx", "args": ["-y", "@google-cloud/cloud-run-mcp"] } -
[Optional] Add default configurations
"cloud-run": { "command": "npx", "args": ["-y", "@google-cloud/cloud-run-mcp"], "env": { "GOOGLE_CLOUD_PROJECT": "PROJECT_NAME", "GOOGLE_CLOUD_REGION": "PROJECT_REGION", "DEFAULT_SERVICE_NAME": "SERVICE_NAME" } }
Using Docker
See Docker's MCP catalog, or use these manual instructions:
-
Install Docker
-
Update the MCP configuration file of your MCP client with the following:
"cloud-run": { "command": "docker", "args": [ "run", "-i", "--rm", "-e", "GOOGLE_APPLICATION_CREDENTIALS", "-v", "/local-directory:/local-directory", "mcp/cloud-run-mcp:latest" ], "env": { "GOOGLE_APPLICATION_CREDENTIALS": "/Users/slim/.config/gcloud/application_default-credentials.json", "DEFAULT_SERVICE_NAME": "SERVICE_NAME" } }
Set up as remote MCP server
[!WARNING]
Do not use the remote MCP server without authentication. In the following instructions, we will use IAM authentication to secure the connection to the MCP server from your local machine. This is important to prevent unauthorized access to your Google Cloud resources.
Run the Cloud Run MCP server itself on Cloud Run with connection from your local machine authenticated via IAM. With this option, you will only be able to deploy code to the same Google Cloud project as where the MCP server is running.
-
Install the Google Cloud SDK and authenticate with your Google account.
-
Log in to your Google Cloud account using the command:
gcloud auth login -
Set your Google Cloud project ID using the command:
gcloud config set project YOUR_PROJECT_ID -
Deploy the Cloud Run MCP server to Cloud Run:
gcloud run deploy cloud-run-mcp --image us-docker.pkg.dev/cloudrun/container/mcp --no-allow-unauthenticatedWhen prompted, pick a region, for example
europe-west1.Note that the MCP server is not publicly accessible, it requires authentication via IAM.
-
[Optional] Add default configurations
gcloud run services update cloud-run-mcp --region=REGION --update-env-vars GOOGLE_CLOUD_PROJECT=PROJECT_NAME,GOOGLE_CLOUD_REGION=PROJECT_REGION,DEFAULT_SERVICE_NAME=SERVICE_NAME,SKIP_IAM_CHECK=false -
Run a Cloud Run proxy on your local machine to connect securely using your identity to the remote MCP server running on Cloud Run:
gcloud run services proxy cloud-run-mcp --port=3000 --region=REGION --project=PROJECT_IDThis will create a local proxy on port 3000 that forwards requests to the remote MCP server and injects your identity.
-
Update the MCP configuration file of your MCP client with the following:
"cloud-run": { "url": "http://localhost:3000/sse" }If your MCP client does not support the
urlattribute, you can use mcp-remote:"cloud-run": { "command": "npx", "args": ["-y", "mcp-remote", "http://localhost:3000/sse"] }
Using MCP Server with OAuth
Cloud Run MCP server supports OAuth as an authentication mechanism. In order to use OAuth, create the OAuth client, and configure a .env file with the appropriate values pertaining to your OAuth client. A .env.example is provided for reference.
The Cloud Run MCP server works seamlessly with Google Cloud SDK OAuth client. In order to leverage the Google Cloud SDK OAuth client, you can use the .env.gcloud-sdk-oauth file as your .env file as follows:
cp .env.gcloud-sdk-oauth .env
node mcp-server.js
Configure MCP Server on Gemini CLI to use OAuth
When the Cloud Run MCP server is started in the OAuth mode, the MCP client should also be configured to use OAuth. You can setup the MCP server in OAuth mode in the Gemini CLI by using the following JSON in the ~/.gemini/settings.json file:
{
"mcpServers": {
"cloud-run": {
"httpUrl": "http://localhost:3000/mcp",
"oauth": {
"enabled": true,
"clientId": "<OAUTH_CLIENT_ID>",
"clientSecret": "<OAUTH_CLIENT_SECRET>"
}
}
}
}
Post the configuration changes as shown above, start the Gemini CLI. You should authenticate the Cloud Run MCP server using the following prompt in the Gemini CLI:
/mcp auth cloud-run
This will take you to the authentication page on your browser, wherein you need to sign in using the appropriate gmail id, and accept the terms and conditions. Once the authentication is succcessful, you can come back to the Gemini CLI, and the Cloud Run MCP server will be ready to use.
The Google Cloud Platform Terms of Service (available at https://cloud.google.com/terms/) and the Data Processing and Security Terms (available at https://cloud.google.com/terms/data-processing-terms) do not apply to any component of the Cloud Run MCP Server software.
Cloud Run Skills
We introduce Cloud Run skills to enable AI agents to perform actions on Cloud Run. You can use these skills with Gemini CLI and other agentic AI tools. The skills are available at Cloud Run Skills.
The Cloud Run skills are based on top of gcloud cli for Cloud Run empowering agents to perform all the actions on the Cloud Run using gcloud, as can be performed by the GCP user using gcloud cli.
In order to use Cloud Run skills:
- Ensure you have the
gcloudCLI installed and authenticated withgcloud auth loginandgcloud auth application-default login. - Set your project with
gcloud config set project [PROJECT_ID]. - Enable the skills on your agentic AI tool. For example, you can enable the skills for Gemini CLI using the following command on your terminal:
gemini skills install https://github.com/GoogleCloudPlatform/cloud-run-mcp.git --path skills/cloud-run
- Once the skills are enabled, you can use them to perform actions on Cloud Run. Here are some of the prompts for you to get started:
-
List the Cloud Run services in the project test-gcp-project in the region us-west1.
-
Deploy the folder /home/username/workspace/hello-world as Cloud Run service hello-world to the project test-gcp-project in the region us-west1.
-
Describe the Cloud Run job hello-job in the project test-gcp-project in the region europe-west1.
Preguntas sobre Cloud Run MCP
¿Cómo agrego Cloud Run MCP a Claude Code?
Ejecuta claude mcp add cloud-run-mcp -- npx -y @google-cloud/cloud-run-mcp en tu terminal. Añade --scope user para que esté disponible en todos los proyectos.
¿Cómo agrego Cloud Run MCP a Cursor?
Abre ~/.cursor/mcp.json y añade el servidor en mcpServers, usando la configuración de Cursor que se muestra en la sección de instalación de arriba.
¿Qué herramientas proporciona Cloud Run MCP?
Expone 8 herramientas, incluidas list_projects, create_project, list_services, get_service, get_service_log.
¿Qué puede hacer el Cloud Run MCP server?
Permite que agentes de IA desplieguen archivos o carpetas locales en Cloud Run, listen e inspeccionen servicios, obtengan logs de servicios y gestionen proyectos de GCP cuando se ejecuta localmente.
¿Cómo instalo el Cloud Run MCP server con Node.js?
Añádelo a la configuración de tu cliente MCP usando el comando npx y el paquete @google-cloud/cloud-run-mcp.
¿El Cloud Run MCP server es compatible con OAuth?
Sí, se puede habilitar la verificación de tokens Bearer de OAuth 2.0 para las solicitudes HTTP/SSE entrantes.
¿Qué herramientas solo están disponibles al ejecutarlo localmente?
deploy-local-folder, list-projects y create-project solo están disponibles cuando el servidor se ejecuta de forma local.
¿Cómo me autentico antes de usar el servidor?
Inicia sesión con gcloud auth login y configura las credenciales predeterminadas de la aplicación (application default credentials).