1. Home
  2. Cloud Run MCP Server
  3. Cloud Run MCP Server for Claude Desktop: Setup & Config

Data as of

Cloud Run MCP Server for Claude Desktop: Setup & Config

Claude Desktop: Cloud Run MCP Server connects agents to application deployment and service inspection on Google Cloud Run.

What you can do with Cloud Run in Claude Desktop

Deploy from an agent and investigate the resulting Cloud Run service without changing integrations.

  • Move application source from an agent workflow into a Cloud Run deployment.
  • Inspect service configuration and error evidence after deployment.

Before you start: Cloud Run in Claude Desktop

  • Node.js, preferably an LTS release
  • Installed Google Cloud SDK
  • Google account authentication and application-default credentials
  • MCP client configured to start the local package

The command matches the README's recommended local Node configuration, not the bare script from config_hint. Prepare credentials with gcloud auth login followed by gcloud auth application-default login. All three environment entries are optional defaults. A remotely hosted server follows a different authenticated setup and does not expose the local-only tools.

Cloud Run Claude Desktop configuration

  1. Choose Claude Desktop configuration scope

    For Cloud Run MCP Server, open macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json. Merge under mcpServers via Settings → Developer → Edit Config when available.

  2. Add Cloud Run MCP Server to Claude Desktop

    Use the cloud-run-mcp entry below in mcpServers. Keep Cloud Run MCP Server's documented stdio connection fields and your other Claude Desktop entries.

  3. Check Cloud Run MCP Server in Claude Desktop

    Cloud Run MCP Server: Fully quit and reopen Claude Desktop; check developer diagnostics.

Config file · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%\Claude\claude_desktop_config.json

JSON
{
  "mcpServers": {
    "cloud-run-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@google-cloud/cloud-run-mcp"
      ],
      "env": {
        "GOOGLE_CLOUD_PROJECT": "<optional project ID used when a request omits it>",
        "GOOGLE_CLOUD_REGION": "<optional deployment region used by default>",
        "DEFAULT_SERVICE_NAME": "<optional fallback name for the Cloud Run service>"
      }
    }
  }
}

Cloud Run tools available to Claude Desktop

Cloud Run's stored tool list documents 7 tools; compare it with Claude Desktop's connected tool list, because the stored list is not a live check.

get-service-log

When Claude Desktop requests get-service-log from Cloud Run, review the action before approving it.

Read a selected service's logs, including error messages.

get-service

When Claude Desktop requests get-service from Cloud Run, review the action before approving it.

Inspect details about one deployed Cloud Run service.

list-services

When Claude Desktop requests list-services from Cloud Run, review the action before approving it.

Discover services within the chosen region and project.

deploy-file-contents

When Claude Desktop requests deploy-file-contents from Cloud Run, review the action before approving it.

Publish an application by supplying its files' contents directly.

deploy-local-folder

When Claude Desktop requests deploy-local-folder from Cloud Run, review the action before approving it.

list-projects

When Claude Desktop requests list-projects from Cloud Run, review the action before approving it.

create-project

When Claude Desktop requests create-project from Cloud Run, review the action before approving it.

Cloud Run: full stored tool descriptions

Troubleshooting Cloud Run in Claude Desktop

  • Fully quit and reopen Claude Desktop for Cloud Run MCP Server. If npx @google-cloud/cloud-run-mcp (Node.js/npm) is missing, check the desktop process's PATH, which may differ from your terminal.
  • In Claude Desktop's Cloud Run MCP Server entry, check DEFAULT_SERVICE_NAME, GOOGLE_CLOUD_PROJECT, GOOGLE_CLOUD_REGION. Keep secrets out of shared screenshots and repositories.
  • Cloud Run MCP Server uses stdio here: Claude Desktop must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
  • Known limitation: Remote instances cannot deploy outside their own hosting project.
  • Known limitation: Folder deployment and project discovery or creation are unavailable in remote mode.
  • Known limitation: Remote access needs authentication; host validation is not enabled by default.
  • General Claude Desktop troubleshooting lives in the /clients/claude-desktop guide.

Cloud Run MCP Server — details. Claude Desktop guide

Frequently asked questions

Claude Desktop loads Cloud Run MCP Server from claude_desktop_config.json: ~/Library/Application Support/Claude/ on macOS, or %APPDATA%\Claude\ on Windows. Open it via Settings → Developer → Edit Config when available.

Claude Desktop's cloud-run-mcp example uses stdio.

Cloud Run MCP Server's Claude Desktop configuration invokes npx @google-cloud/cloud-run-mcp (Node.js/npm).

Claude Desktop's Cloud Run MCP Server example references DEFAULT_SERVICE_NAME, GOOGLE_CLOUD_PROJECT, GOOGLE_CLOUD_REGION. Check these names if startup or authentication fails; the example alone does not distinguish required from optional values.

Cloud Run MCP Server's stored list contains 7 tools, including get-service-log, get-service, list-services. Compare those names with Claude Desktop's connected tool list; the stored list is not a live check.

The local-only set consists of create-project, deploy-local-folder, and list-projects. A remote instance is also confined to deployments within its hosting project.

A local gcloud proxy forwards requests to the remote service using the user's identity. The remote MCP deployment itself is not made publicly accessible.