Cloud Run MCP Server for Cursor: Setup & Config

What you can do with Cloud Run in Cursor

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

• Use saved deployment defaults with the supplied deploy and logs prompts.
• Discover or create Google Cloud projects when operating the server locally.

Before you start: Cloud Run in Cursor

• 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 Cursor configuration

1. Choose Cursor configuration scope

   For Cloud Run MCP Server, open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.

2. Add Cloud Run MCP Server to Cursor

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

3. Check Cloud Run MCP Server in Cursor

   Cloud Run MCP Server: Enable in Cursor’s MCP settings; inspect tools.

{
  "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 Cursor

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

get-service-log

Find get-service-log under Cloud Run in Cursor's MCP settings; inspect its arguments when the agent requests a call.

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

get-service

Find get-service under Cloud Run in Cursor's MCP settings; inspect its arguments when the agent requests a call.

list-services

Find list-services under Cloud Run in Cursor's MCP settings; inspect its arguments when the agent requests a call.

deploy-file-contents

Find deploy-file-contents under Cloud Run in Cursor's MCP settings; inspect its arguments when the agent requests a call.

deploy-local-folder

Find deploy-local-folder under Cloud Run in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Use a source directory for deployment; exposed only by a locally running instance.

list-projects

Find list-projects under Cloud Run in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Discover available Google Cloud projects in local mode.

create-project

Find create-project under Cloud Run in Cursor's MCP settings; inspect its arguments when the agent requests a call.

In local mode, create a project linked to the first available billing account, optionally choosing its ID.

Cloud Run: full stored tool descriptions

Troubleshooting Cloud Run in Cursor

• Cursor must find npx @google-cloud/cloud-run-mcp (Node.js/npm) for Cloud Run MCP Server. Enable the project/user entry in MCP settings and inspect its tools.
• Review DEFAULT_SERVICE_NAME, GOOGLE_CLOUD_PROJECT, GOOGLE_CLOUD_REGION for Cloud Run MCP Server before sharing project .cursor/mcp.json; project scope travels with the repository.
• Cloud Run MCP Server uses stdio here: Cursor 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 Cursor troubleshooting lives in the /clients/cursor guide.

Frequently asked questions