Official MCP Server to deploy to Google Cloud Run.
Official MCP Server to deploy to Google Cloud Run. Exposed over MCP by the google cloud run mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
Enable MCP-compatible AI agents to deploy apps to Cloud Run.
Everything the assistant can do here goes through one of these:
deploy-file-contents — Deploys files to Cloud Run by providing their contents directlylist-services — Lists Cloud Run services in a given project and regionget-service — Gets details for a specific Cloud Run serviceget-service-log — Gets Logs and Error Messages for a specific Cloud Run servicedeploy-local — folder*: Deploys a local folder to a Google Cloud Run servicelist — projects*: Lists available GCP projectscreate — project*: Creates a new GCP project and attach it to the first available billing account. A project ID can be optionally specifiedSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
You will need 8 environment variables: GOOGLE_CLOUD_PROJECT, GOOGLE_CLOUD_REGION, DEFAULT_SERVICE_NAME, GOOGLE_APPLICATION_CREDENTIALS, PROJECT_REGION, YOUR_PROJECT_ID, PROJECT_ID, OAUTH_CLIENT_ID. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Google Cloud Run's toolset — deploy-file-contents, list-services, get-service and 4 more — is a fair guide to whether it matches your workflow.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| 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. |
| list | projects\*: Lists available GCP projects. |
| create | project\*: Creates a new GCP project and attach it to the first available billing account. A project ID can be optionally specified. |
"mcpServers":{
"cloud-run": {
"command": "npx",
"args": ["-y", "@google-cloud/cloud-run-mcp"]
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| GOOGLE_CLOUD_PROJECT | Configuration value read at startup. | Optional |
| GOOGLE_CLOUD_REGION | Configuration value read at startup. | Optional |
| DEFAULT_SERVICE_NAME | Configuration value read at startup. | Optional |
| GOOGLE_APPLICATION_CREDENTIALS | Configuration value read at startup. | Optional |
| PROJECT_REGION | Configuration value read at startup. | Optional |
| YOUR_PROJECT_ID | Configuration value read at startup. | Optional |
| PROJECT_ID | Configuration value read at startup. | Optional |
| OAUTH_CLIENT_ID | Configuration value read at startup. | Optional |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.