How to add Cloud Run MCP Server to Cursor

Deploy apps and folders to Google Cloud Run directly from MCP-compatible AI agents. Paste the config into ~/.cursor/mcp.json and restart Cursor.

Last updated June 14, 2026 · 617★ · stdio · oauth

Cursor config for Cloud Run MCP Server

npx -y @google-cloud/cloud-run-mcp

{
  "mcpServers": {
    "cloud-run-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@google-cloud/cloud-run-mcp"
      ]
    }
  }
}

Setup steps

1Open Cursor → Settings → MCP → Add new MCP server (or edit ~/.cursor/mcp.json directly).
2Paste the Cloud Run MCP Server config below into the "mcpServers" object.
3Fill in placeholder secrets, then save.
4Cursor reloads MCP servers automatically — check Settings → MCP for a green status dot.
5Ask Cursor to use one of Cloud Run MCP Server's tools to confirm it's connected.

Before you start

Node.js (LTS recommended) for the Node.js setup, or Docker for the container setup
Google Cloud SDK (gcloud) installed and authenticated
Authenticate with `gcloud auth login` and `gcloud auth application-default login`
A Google Cloud account with access to Cloud Run / a GCP project

What Cloud Run MCP Server can do in Cursor

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 (only available when running locally).

list-projects

Lists available GCP projects (only available when running locally).

create-project

Creates a new GCP project and attaches it to the first available billing account; a project ID can optionally be specified (only available when running locally).

Security

Local mode uses your Google Cloud application-default credentials, granting the server the deploy and project-management permissions of your gcloud identity. For remote mode, do NOT expose the server without authentication — the docs use IAM auth via `gcloud run services proxy` and deploy with `--no-allow-unauthenticated`. `SKIP_IAM_CHECK` defaults to `true` (makes deployed services public); set it to `false` to enforce IAM checks. `ENABLE_HOST_VALIDATION` (with `ALLOWED_HOSTS`) can be enabled to prevent DNS rebinding attacks. The tools `deploy-local-folder`, `list-projects`, and `create-project` are only available when running locally.

Cloud Run MCP Server + Cursor FAQ

Where is the Cursor config file?

Cursor reads MCP servers from ~/.cursor/mcp.json. Paste the Cloud Run MCP Server config there under the "mcpServers" key and restart the client.

Is Cloud Run MCP Server safe to use with Cursor?

Is this for hosting MCP servers on Cloud Run?

No. This repository is an MCP server used to deploy your code to Cloud Run. To learn how to host MCP servers on Cloud Run, see the Cloud Run documentation referenced in the README.

How do I run it as a remote server safely?

Deploy the server to Cloud Run with `--no-allow-unauthenticated`, then run `gcloud run services proxy` on your machine to connect securely via your IAM identity. Point your MCP client at `http://localhost:3000/sse` (or use mcp-remote if your client lacks `url` support). Never expose the remote server without authentication.

Which tools require running locally?

`deploy-local-folder`, `list-projects`, and `create-project` are only available when the server runs locally.

View repo Full Cloud Run MCP Server page