# Google Cloud Run MCP server > Deploy Cloud Run services from container images, source archives or inline files, and inspect existing services. - Listing: https://mcp.tc/i/cloud-run - Connect: use the server's own URL `https://run.googleapis.com/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint. - Type: remote (Streamable HTTP) - Auth: OAuth sign-in - Category: [Cloud & DevOps](https://mcp.tc/c/cloud-devops) - Vendor: Google Cloud - Verified: yes, mcp.tc checked that this is the official server (https://mcp.tc/verify). It says who runs the server, not that it is safe. - Homepage: ## About Connects an assistant to Google Cloud Run in a given project and region. It can list services, read a service's URI and deploy status, and deploy a service from a container image, a .tar.gz source archive or source files sent inline. A deploy prompt is also provided for deploying the current working directory. The server is hosted by Google at run.googleapis.com/mcp and uses streamable HTTP. Access is controlled by Google OAuth 2.0 and IAM permissions on your Google Cloud project. Deploy tools change live services, so review requests before approving them. ## What it can do - List Cloud Run services in a project and region - Get a service's URI and deployment status - Deploy a service from an Artifact Registry or Docker Hub image - Deploy from a self-contained .tar.gz source archive - Deploy from source files embedded in the request - Use the deploy prompt for the current working directory ## Tools (5) - `get_service`: Get a Cloud Run service's details, such as its URI and whether the deploy succeeded. (read-only) - `list_services`: List Cloud Run services in a Google Cloud project and region. (read-only) - `deploy_service_from_image`: Deploy a container image from Artifact Registry or Docker Hub as a Cloud Run service. (can modify or delete data) - `deploy_service_from_archive`: Deploy a service from a self-contained .tar.gz source archive uploaded to Cloud Storage. (can modify or delete data) - `deploy_service_from_file_contents`: Deploy a service from source files embedded in the request, skipping the build step. (can modify or delete data) ## Example prompts - "List the Cloud Run services in my project my-project in us-central1" - "Is the checkout service in europe-west1 deployed successfully, and what is its URL?" - "Deploy the image us-docker.pkg.dev/my-project/app/api:latest to Cloud Run as api" - "Deploy this Node.js app from the current directory to Cloud Run" ## Install ### Claude Code 1. Run this in a terminal, in your project folder: ```bash claude mcp add --transport http cloud-run https://run.googleapis.com/mcp ``` 2. Start Claude Code, type `/mcp`, pick **cloud-run** and choose **Authenticate**. A browser window opens for the Google Cloud sign-in. Add `--scope user` to make it available in every project, not just this one. ### Claude Desktop 1. Open **Settings → Connectors** and click **Add custom connector**. 2. Name it **Google Cloud Run** and paste this URL: ```url https://run.googleapis.com/mcp ``` 3. Click **Add**, then **Connect**, and sign in when Google Cloud asks. Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too. ### claude.ai 1. Open the connector form on claude.ai. This button fills in the name and URL for you: [Add to claude.ai]() (opens connector settings) 2. Check that the URL reads `https://run.googleapis.com/mcp` and click **Add**. 3. Click **Connect** and sign in when Google Cloud asks. Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**. ### ChatGPT 1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**. 2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server. 3. Paste `https://run.googleapis.com/mcp` as the server URL and choose **OAuth**. ChatGPT sends you to Google Cloud to sign in. Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts. ### Cursor [Add to Cursor]() (opens Cursor) Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project): `mcp.json`: ```json { "mcpServers": { "cloud-run": { "url": "https://run.googleapis.com/mcp" } } } ``` Cursor shows **Needs login** next to the server. Click it to sign in. ### VS Code [Install in VS Code]() (opens VS Code) Or from a terminal: ```bash code --add-mcp '{"name":"cloud-run","type":"http","url":"https://run.googleapis.com/mcp"}' ``` Or commit it to the repo in `.vscode/mcp.json`: `.vscode/mcp.json`: ```json { "servers": { "cloud-run": { "type": "http", "url": "https://run.googleapis.com/mcp" } } } ``` VS Code asks you to sign in the first time the server starts. ### Devin Desktop 1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows): `mcp_config.json`: ```json { "mcpServers": { "cloud-run": { "serverUrl": "https://run.googleapis.com/mcp" } } } ``` 2. Refresh the MCP server list in Cascade and sign in when asked. Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers. ### Codex ```bash codex mcp add cloud-run --url https://run.googleapis.com/mcp codex mcp login cloud-run ``` Or edit `~/.codex/config.toml` directly: `config.toml`: ```toml [mcp_servers.cloud-run] url = "https://run.googleapis.com/mcp" ``` ### Gemini CLI ```bash gemini mcp add --transport http cloud-run https://run.googleapis.com/mcp ``` Then, inside Gemini CLI, run `/mcp auth cloud-run` to sign in. This adds it to the current project. Add `-s user` to use it everywhere. ### Any client Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file. ```json { "mcpServers": { "cloud-run": { "type": "http", "url": "https://run.googleapis.com/mcp" } } } ``` Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE. Client only starts local servers? Bridge it with `npx -y mcp-remote https://run.googleapis.com/mcp`. ## Details - Server version: ESF - MCP protocol version: 2025-11-25 - Last checked: 2026-10-03 (reachable) - Listed: 2026-10-03 - Updated: 2026-10-03 --- Source: https://mcp.tc/i/cloud-run (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report