PlugWiki
@google-cloud/cloud-run-mcp logo

Google Cloud Run MCP Server: Setup for Claude, Cursor and Other Apps

OfficialLocal
Getnpm@google-cloud/cloud-run-mcpgooglecloudplatform/cloud-run-mcp

Lets Claude, Cursor or another assistant deploy code and container images to Google Cloud Run and read the logs of your services.

This is Google's own Cloud Run server. It runs on your computer and uses the Google Cloud login you set up with gcloud, so it acts with your permissions. You need Node.js and the Google Cloud SDK, and you must run both gcloud login commands from the README first.

By default it deploys services that anyone on the internet can reach. Set SKIP_IAM_CHECK to false to turn that off. The README also lists tools with hyphens, but the code registers them with underscores.

Good for

  • Developers who want to ship a prototype to Cloud Run straight from an assistant
  • Google Cloud users who debug a failing service by asking for its logs
  • Teams trying Gemini CLI or AI IDEs for deploys

Works in

5 supported · 7 should work

Tap an app to see how to set it up and any known problems.

Install @google-cloud/cloud-run MCP

Claude Code

  1. 1

    Copy this prompt.

    Add the @google-cloud/cloud-run MCP server to Claude Code. Run this command:
    
    claude mcp add cloud-run-mcp -- npx -y @google-cloud/cloud-run-mcp
    
    Then check that it loaded and tell me if I need to sign in or restart.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js, Google Cloud SDK, logged in.

First run gcloud auth login and gcloud auth application-default login. The npx command comes from the README. Add SKIP_IAM_CHECK=false to the env block to keep new services private. The README names Gemini CLI, Claude Desktop, Cursor, VS Code and Windsurf only as clients to follow their own config guides; the per-client files here are generated from the README command.

Built from the package data we hold. Not yet tested by us.

Tools

  • Lists your Google Cloud projects

    Returns the Google Cloud projects your local gcloud login can see. Only available when the server runs on your machine.

    Try: “Which Google Cloud projects can I deploy to?”

    Network · list_projects

  • Creates a Google Cloud project

    Creates a new project, optionally with an ID you choose, and tries to attach it to the first billing account on your login. Only available when the server runs on your machine.

    Try: “Create a new project called demo-site-123.”

    Write · create_project

  • Lists Cloud Run services

    Returns the Cloud Run services in a project and region.

    Try: “What services are running in my-project in europe-west1?”

    Network · list_services

  • Shows one Cloud Run service

    Returns the details of a single service, including its URL and when it was last deployed.

    Try: “Show me the details and URL of the api service.”

    Network · get_service

  • Reads logs and errors of a service

    Returns recent log lines and error messages for one Cloud Run service so the assistant can find why a deploy failed.

    Try: “Why is my api service returning errors? Check the logs.”

    Network · get_service_log

  • Deploys a folder from your computer

    Uploads a folder you name by absolute path, builds it in Google Cloud and deploys it to a Cloud Run service. Only available when the server runs on your machine.

    Try: “Deploy the current folder to Cloud Run as my-app.”

    Write · deploy_local_folder

  • Deploys files from the chat

    Takes file names and contents the assistant provides, builds them in Google Cloud and deploys them. Use it when the code only exists in the conversation.

    Try: “Write a tiny Node web server and deploy it to Cloud Run.”

    Write · deploy_file_contents

  • Deploys an existing container image

    Deploys a container image from a URL you give to a Cloud Run service. The README does not list this tool, but the code registers it.

    Try: “Deploy us-docker.pkg.dev/my-project/app:latest to Cloud Run.”

    Write · deploy_container_image

Read from the source code

Permissions

high risk · 4 things to watch

High risk

It can create projects, deploy services and read logs in your Google Cloud account, and new services are open to the public by default. Use a project you can afford to experiment in and set SKIP_IAM_CHECK to false before deploying anything private.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • Deployed services are public by default

    SKIP_IAM_CHECK defaults to true, which sets the service to allow any caller. Set SKIP_IAM_CHECK to false in the server env before you deploy anything private. github.com

  • create_project links a billing account

    It tries to attach the new project to the first billing account on your login, so costs can start. Ask the assistant to confirm the project ID before it runs. github.com

  • deploy_local_folder uploads a whole folder

    Everything in the folder you name is sent to Google Cloud to be built. Check the folder for secrets such as .env files first. github.com

  • Deploys create cloud resources in your project

    Deploys can create storage buckets and an Artifact Registry repository besides the service. Remove them in the console when you stop using the project. github.com

Security advisories

No published security advisories as of Nov 1, 2026.

Technical details
Talks toGoogle Cloud APIs (Cloud Run, Cloud Build, Artifact Registry, Storage, Logging, Resource Manager, Billing)
Sign-in and keysCredentials stay in your local gcloud application-default login. The server stores nothing itself.
Scopes
  • Your gcloud application-default credentials, with whatever roles your Google account has. No narrower scope is set by the server.

Questions

Is the Cloud Run MCP server official?

Yes. It lives in Google's GoogleCloudPlatform GitHub organization and is published to npm as @google-cloud/cloud-run-mcp.

Do I need an API key?

No. Install the Google Cloud SDK, then run gcloud auth login and gcloud auth application-default login. The server uses that login.

Are my deployed services public?

Yes, by default. SKIP_IAM_CHECK is true unless you set it to false, and the README calls that its recommended way to make a service public.

Can it delete services or projects?

No. None of the eight tools deletes anything. It can create projects and deploy over existing services.

Can I run it read-only?

No. There is no read-only switch. Use a Google account that only has viewer roles if you want to prevent deploys.

Does it work in Gemini CLI?

Yes. The README documents a Gemini CLI extension you add with gemini extensions install, plus the two gcloud login commands.

Can I use it with Docker?

Yes. The README shows a Docker setup using the mcp/cloud-run-mcp image, and it is also in Docker's MCP catalog.

Information

updated Nov 2, 2026

Publisher
Official
Package
@google-cloud/cloud-run-mcp
Registry
npm
Transport
stdio
Auth
None
Version
1.11.0
License
Apache-2.0
Last commit
Oct 31, 2026

GitHubnpmChangelogIssues

Sources

Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.

Show all 5
  1. README.md · github.com
  2. register-tools.js · github.com
  3. tools.js · github.com
  4. mcp-server.js · github.com
  5. deployer.js · github.com

Facts from the official MCP registry, GitHub, npm, PyPI and the Docker catalog. Updated Nov 2, 2026.