---
title: "Google Cloud Run MCP server for AI agents - actionlake"
description: "Give Claude 58 Google Cloud Run actions through one MCP server: instances, jobs, services. Your agent never holds the credential. 100,000 calls a month free."
canonical: https://actionlake.com/connectors/google-cloud-run
updated: 2026-10-23
---

Connectors · Developer & infrastructure

# Google Cloud Run MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Google Cloud Run and the rest of your systems. It gives your agent 58 Google Cloud Run actions (32 reads, 12 writes and 14 that wait for a confirmation) and holds the Google Cloud Run credential itself, so the agent never does. It paces Google Cloud Run's limits and records every call. Connecting Google Cloud Run needs your own Google Cloud Run OAuth app and one admin sign-in.

[Connect Google Cloud Run free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing)

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

`claude mcp add --transport http actionlake https://connect.actionlake.com/mcp`

the first call

```
do {
  action: "gcp_cloud_run.locations.export_project_metadata",
  intent: "check which Google Cloud Run account is connected"
}
# Projects locations: export project metadata · read · 1 upstream call
```

- 58 actions in one signed file
- 32 read look, never change
- 12 write create and update
- 14 wait for a yes destructive, confirmed first

Set up

## Connect Google Cloud Run in three steps.

1. 01
   ### Add actionlake to Claude.
   Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.
   `https://connect.actionlake.com/mcp`
2. 02
   ### Connect Google Cloud Run.
   OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Google Cloud Run, an admin signs in once, and you paste the app's client id and secret and the tokens from that sign-in; actionlake renews the access token from then on. actionlake stores what you paste write-only, sealed under your tenant's key.
   Before the first sign-in, Google Cloud Run needs an OAuth app of your own, registered in its developer portal. actionlake has no Google Cloud Run app to lend you.
   - `access_token` Access token from one sign-in with your own OAuth app
   - `refresh_token` Refresh token from the same sign-in; the access token is renewed from it
   - `client_id` Google OAuth client id (Google Cloud console > APIs & Services > Credentials; enable the Cloud Run Admin API on the…
   - `client_secret` Google OAuth client secret
   ```
   account { op: "connections.requirements", service: "gcp_cloud_run" }
   # free: exactly what to paste, and what is found for you
   ```
3. 03
   ### Make the first call. Check before a write.
   Ask in plain words; Claude picks the action. Before anything changes, `check` validates the call and prices it, for free.
   ```
   do    { action: "gcp_cloud_run.locations.export_project_metadata" }
   # projects locations: export project metadata · read · 1 upstream call
   check { action: "gcp_cloud_run.jobs.create", input: { … } }
   # free: inputs, permissions, cost and confirmations, nothing sent
   ```

Google Cloud Run at a glance

**Sign-in**

OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Google Cloud Run, an admin signs in once, and you paste the app's client id and secret and the tokens from that sign-in; actionlake renews the access token from then on.

**You provide**

`access_token` `refresh_token` `client_id` `client_secret`

**Limits we pace to**

600 calls a minute, per connection

**API covered**

Google Cloud Run Admin API v2 (services, revisions, jobs, executions, tasks, worker pools, instances, operations) API run v2 (Discovery revision 20261016)`run.googleapis.com`

**Built from**

Google Cloud Run's documentation, read 23 October 2026[run.googleapis.com](https://run.googleapis.com/$discovery/rest?version=v2) [cloud.google.com](https://cloud.google.com/run/docs/reference/rest)

**Service file**

Version 1.0.0, signed (Ed25519)

**Cached reads**

25 of 32 reads, for up to 5 minutes; a write clears what it affects

**Shared entities**

2, so ask can line Google Cloud Run up with your other systems

**Data**

Processed and stored in Sydney, Australia. No US region yet

Capabilities

## What an AI agent can do in Google Cloud Run.

58 actions in 11 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

- **32** read look, never change
- **12** write create and update
- **14** destructive wait for a confirmation

1. ### Instances
   10
   4 read · 3 write · 3 destructive
   Projects locations instances: create · Projects locations instances: list · Projects locations instances: test iam permissions · Projects locations instances: get
2. ### Jobs
   9
   4 read · 3 write · 2 destructive
   Projects locations jobs: list · Projects locations jobs: create · Projects locations jobs: get · Projects locations jobs: patch
3. ### Services
   8
   4 read · 2 write · 2 destructive
   Projects locations services: list · Projects locations services: create · Projects locations services: get · Projects locations services: patch
4. ### Worker pools
   8
   4 read · 2 write · 2 destructive
   Projects locations worker pools: create · Projects locations worker pools: list · Projects locations worker pools: test iam permissions · Projects locations worker pools: get
5. ### Jobs executions
   5
   3 read · 0 write · 2 destructive
   Projects locations jobs executions: list · Projects locations jobs executions: export status · Projects locations jobs executions: get · Projects locations jobs executions: delete
6. ### Locations
   4
   3 read · 1 write · 0 destructive
   Projects locations: export image · Projects locations: export image metadata · Projects locations: export metadata · Projects locations: export project metadata
7. ### Operations
   4
   3 read · 0 write · 1 destructive
   Projects locations operations: list · Projects locations operations: wait · Projects locations operations: get · Projects locations operations: delete
8. ### Services revisions
   4
   3 read · 0 write · 1 destructive
   Projects locations services revisions: list · Projects locations services revisions: export status · Projects locations services revisions: get · Projects locations services revisions: delete

**3 more areas · 6 actions**

- Worker pools revisions **3**
- Jobs executions tasks **2**
- Builds **1**

Top actions

## The Google Cloud Run API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 10 of Google Cloud Run's 10 action names are shared with at least one other connector, so an agent learns them once.

| Action | What it does | Effect | Same name in |
| --- | --- | --- | --- |
| `gcp_cloud_run.jobs.list` Projects locations jobs: list | Lists Jobs. | read | `infra.job.list` 12 connectors |
| `gcp_cloud_run.services.list` Projects locations services: list | Lists Services. | read | `infra.container_service.list` 11 connectors |
| `gcp_cloud_run.jobs.create` Projects locations jobs: create | Creates a Job. | write | `infra.job.create` 10 connectors |
| `gcp_cloud_run.services.create` Projects locations services: create | Creates a new Service in a given project and location. | write | `infra.container_service.create` 8 connectors |
| `gcp_cloud_run.services.delete` Projects locations services: delete | Deletes a Service. | destructive | `infra.container_service.delete` 11 connectors |
| `gcp_cloud_run.jobs.run` Projects locations jobs: run | Triggers creation of a new Execution of this Job. | write | this connector |
| `gcp_cloud_run.operations.list` Projects locations operations: list | Lists operations that match the specified filter in the request. | read | this connector |
| `gcp_cloud_run.operations.wait` Projects locations operations: wait | Waits until the specified long-running operation is done or reaches at most a specified timeout, returning the latest state. | read | this connector |
| `gcp_cloud_run.jobs.test_iam_permissions` Projects locations jobs: test iam permissions | Returns permissions that a caller has on the specified Project. | read | this connector |
| `gcp_cloud_run.services.test_iam_permissions` Projects locations services: test iam permissions | Returns permissions that a caller has on the specified Project. | read | this connector |
| `gcp_cloud_run.services_revisions.list` Projects locations services revisions: list | Lists Revisions from a given Service, or from a given location. | read | this connector |
| `gcp_cloud_run.builds.submit` Projects locations builds: submit | Submits a build in a given project. | write | this connector |

Try it

## Prompts to paste into Claude.

Each one names the Google Cloud Run actions it will call, so you know what it reads and what it changes before you send it.

1. Read read
   Projects locations: export project metadata in Google Cloud Run and tell me what stands out.
   calls `gcp_cloud_run.locations.export_project_metadata`
2. Write write
   Projects locations jobs: create in Google Cloud Run. Show me exactly what you will send before you save it.
   calls `gcp_cloud_run.jobs.create`

Governance for Google Cloud Run

## Destructive actions wait for a yes.

14 Google Cloud Run actions are destructive. These are all of them:

- Projects locations services: delete `gcp_cloud_run.services.delete`
- Projects locations jobs: delete `gcp_cloud_run.jobs.delete`
- Projects locations operations: delete `gcp_cloud_run.operations.delete`
- Projects locations jobs: set iam policy `gcp_cloud_run.jobs.set_iam_policy`
- Projects locations services: set iam policy `gcp_cloud_run.services.set_iam_policy`
- Projects locations jobs executions: delete `gcp_cloud_run.jobs_executions.delete`
- Projects locations services revisions: delete `gcp_cloud_run.services_revisions.delete`
- Projects locations jobs executions: cancel `gcp_cloud_run.jobs_executions.cancel`
- Projects locations instances: stop `gcp_cloud_run.instances.stop`
- Projects locations instances: delete `gcp_cloud_run.instances.delete`
- Projects locations worker pools: delete `gcp_cloud_run.worker_pools.delete`
- Projects locations instances: set iam policy `gcp_cloud_run.instances.set_iam_policy`
- Projects locations worker pools: set iam policy `gcp_cloud_run.worker_pools.set_iam_policy`
- Projects locations worker pools revisions: delete `gcp_cloud_run.worker_pools_revisions.delete`

A destructive action runs only with `confirm: true`. Under the `human` policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

do gcp_cloud_run.services.delete confirm_policy: **human**

Projects locations services: delete?

**intent:** the user asked me to projects locations services: delete

run suspended · waiting for a named person · key _gcp-cloud-run-agent_ cannot confirm itself

In the console, or from an emailed signed link.

a key for this connector

```
account {
  op: "keys.create", name: "gcp-cloud-run-agent",
  allowed_actions: ["gcp_cloud_run.*"], cap_calls: 2000,
  confirm_policy: "human_for_writes",
  approval_rules: [
    { match: "gcp_cloud_run.services.delete", approver: "lead@example.com" },
    { match: "gcp_cloud_run.jobs.delete", approver: "lead@example.com" },
    { match: "gcp_cloud_run.operations.delete", approver: "lead@example.com" }
  ]
}
```

Illustrative. Scoped to Google Cloud Run only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

## What Google Cloud Run costs on actionlake.

Every Google Cloud Run action is one upstream call, the only thing actionlake bills. Searching, `check`, `cost`, `account` and any call Google Cloud Run refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

- 1 upstream call per action all 58 Google Cloud Run actions
- 9 actions page each page of a long list is one call
- 25 reads can be cached a cache hit costs nothing
- 100,000 calls a month, free paid plans from US$49 a month for 250,000

[See pricing](https://actionlake.com/pricing)

Action index

## Every Google Cloud Run action.

58 actions by area: the id your agent calls, what it does, and its effect.

**Instances 10**

- `gcp_cloud_run.instances.create` Projects locations instances: create write
- `gcp_cloud_run.instances.delete` Projects locations instances: delete destructive
- `gcp_cloud_run.instances.get` Projects locations instances: get read
- `gcp_cloud_run.instances.get_iam_policy` Projects locations instances: get iam policy read
- `gcp_cloud_run.instances.list` Projects locations instances: list read
- `gcp_cloud_run.instances.patch` Projects locations instances: patch write
- `gcp_cloud_run.instances.set_iam_policy` Projects locations instances: set iam policy destructive
- `gcp_cloud_run.instances.start` Projects locations instances: start write
- `gcp_cloud_run.instances.stop` Projects locations instances: stop destructive
- `gcp_cloud_run.instances.test_iam_permissions` Projects locations instances: test iam permissions read

**Jobs 9**

- `gcp_cloud_run.jobs.create` Projects locations jobs: create write
- `gcp_cloud_run.jobs.delete` Projects locations jobs: delete destructive
- `gcp_cloud_run.jobs.get` Projects locations jobs: get read
- `gcp_cloud_run.jobs.get_iam_policy` Projects locations jobs: get iam policy read
- `gcp_cloud_run.jobs.list` Projects locations jobs: list read
- `gcp_cloud_run.jobs.patch` Projects locations jobs: patch write
- `gcp_cloud_run.jobs.run` Projects locations jobs: run write
- `gcp_cloud_run.jobs.set_iam_policy` Projects locations jobs: set iam policy destructive
- `gcp_cloud_run.jobs.test_iam_permissions` Projects locations jobs: test iam permissions read

**Services 8**

- `gcp_cloud_run.services.create` Projects locations services: create write
- `gcp_cloud_run.services.delete` Projects locations services: delete destructive
- `gcp_cloud_run.services.get` Projects locations services: get read
- `gcp_cloud_run.services.get_iam_policy` Projects locations services: get iam policy read
- `gcp_cloud_run.services.list` Projects locations services: list read
- `gcp_cloud_run.services.patch` Projects locations services: patch write
- `gcp_cloud_run.services.set_iam_policy` Projects locations services: set iam policy destructive
- `gcp_cloud_run.services.test_iam_permissions` Projects locations services: test iam permissions read

**Worker pools 8**

- `gcp_cloud_run.worker_pools.create` Projects locations worker pools: create write
- `gcp_cloud_run.worker_pools.delete` Projects locations worker pools: delete destructive
- `gcp_cloud_run.worker_pools.get` Projects locations worker pools: get read
- `gcp_cloud_run.worker_pools.get_iam_policy` Projects locations worker pools: get iam policy read
- `gcp_cloud_run.worker_pools.list` Projects locations worker pools: list read
- `gcp_cloud_run.worker_pools.patch` Projects locations worker pools: patch write
- `gcp_cloud_run.worker_pools.set_iam_policy` Projects locations worker pools: set iam policy destructive
- `gcp_cloud_run.worker_pools.test_iam_permissions` Projects locations worker pools: test iam permissions read

**Jobs executions 5**

- `gcp_cloud_run.jobs_executions.cancel` Projects locations jobs executions: cancel destructive
- `gcp_cloud_run.jobs_executions.delete` Projects locations jobs executions: delete destructive
- `gcp_cloud_run.jobs_executions.export_status` Projects locations jobs executions: export status read
- `gcp_cloud_run.jobs_executions.get` Projects locations jobs executions: get read
- `gcp_cloud_run.jobs_executions.list` Projects locations jobs executions: list read

**Locations 4**

- `gcp_cloud_run.locations.export_image` Projects locations: export image write
- `gcp_cloud_run.locations.export_image_metadata` Projects locations: export image metadata read
- `gcp_cloud_run.locations.export_metadata` Projects locations: export metadata read
- `gcp_cloud_run.locations.export_project_metadata` Projects locations: export project metadata read

**Operations 4**

- `gcp_cloud_run.operations.delete` Projects locations operations: delete destructive
- `gcp_cloud_run.operations.get` Projects locations operations: get read
- `gcp_cloud_run.operations.list` Projects locations operations: list read
- `gcp_cloud_run.operations.wait` Projects locations operations: wait read

**Services revisions 4**

- `gcp_cloud_run.services_revisions.delete` Projects locations services revisions: delete destructive
- `gcp_cloud_run.services_revisions.export_status` Projects locations services revisions: export status read
- `gcp_cloud_run.services_revisions.get` Projects locations services revisions: get read
- `gcp_cloud_run.services_revisions.list` Projects locations services revisions: list read

**Worker pools revisions 3**

- `gcp_cloud_run.worker_pools_revisions.delete` Projects locations worker pools revisions: delete destructive
- `gcp_cloud_run.worker_pools_revisions.get` Projects locations worker pools revisions: get read
- `gcp_cloud_run.worker_pools_revisions.list` Projects locations worker pools revisions: list read

**Jobs executions tasks 2**

- `gcp_cloud_run.jobs_executions_tasks.get` Projects locations jobs executions tasks: get read
- `gcp_cloud_run.jobs_executions_tasks.list` Projects locations jobs executions tasks: list read

**Builds 1**

- `gcp_cloud_run.builds.submit` Projects locations builds: submit write

Questions

## The Google Cloud Run MCP server, answered.

**Is there a Google Cloud Run MCP server for Claude?**

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 58 Google Cloud Run actions across instances, jobs, services and worker pools, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Google Cloud Run.

**What do I need to connect Google Cloud Run?**

Your own Google Cloud Run OAuth app, registered with Google Cloud Run (its client id and client secret), and the access and refresh tokens from one admin sign-in. actionlake has no Google Cloud Run app of its own, so this is not a one-step consent. actionlake renews the access token as it expires. The free call account { op: "connections.requirements", service: "gcp_cloud_run" } lists exactly what to paste.

**Can an AI agent delete or change things in Google Cloud Run?**

Only if its key allows it, and only with an explicit confirmation. 14 Google Cloud Run actions are destructive, including projects locations services: delete, projects locations jobs: delete and projects locations operations: delete. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

**Will an AI agent use up my Google Cloud Run API limit?**

actionlake paces every call to the limits in the Google Cloud Run service file: 600 calls a minute per connection. Repeated reads are answered from cache (25 Google Cloud Run actions can be), which never reaches Google Cloud Run.

**What does a Google Cloud Run action cost?**

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (9 Google Cloud Run actions page). Cache hits, searches, dry runs and calls Google Cloud Run refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

**Which Google Cloud Run API does it cover?**

The Google Cloud Run Admin API v2 (services, revisions, jobs, executions, tasks, worker pools, instances, operations) API run v2 (Discovery revision 20261016) at run.googleapis.com. It is built from Google Cloud Run's documentation as read on 23 October 2026. 58 actions in 11 areas, each one in the signed service file (version 1.0.0).

**Does actionlake keep my Google Cloud Run data, and where?**

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Google Cloud Run credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

**Which AI clients can use it?**

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

## More connectors like Google Cloud Run

Shares the most action names with

- [Render 8](https://actionlake.com/connectors/render)
- [Northflank 6](https://actionlake.com/connectors/northflank)
- [Veeam Backup & Replication 5](https://actionlake.com/connectors/veeam-backup-and-replication)
- [Veeam Backup for Microsoft 365 5](https://actionlake.com/connectors/veeam-backup-for-microsoft-365)
- [Coolify 4](https://actionlake.com/connectors/coolify)
- [Fly.io Machines 4](https://actionlake.com/connectors/fly-io-machines)

Joins with, on shared entities

- [Azure Container Apps 2](https://actionlake.com/connectors/azure-container-apps)
- [Google Cloud Document AI 2](https://actionlake.com/connectors/google-cloud-document-ai)
- [Azure AI Document Intelligence 2](https://actionlake.com/connectors/azure-ai-document-intelligence)
- [Google Vertex AI 1](https://actionlake.com/connectors/google-vertex-ai)
- [DigitalOcean 1](https://actionlake.com/connectors/digitalocean)
- [Azure App Service (Web Apps and Functions) 1](https://actionlake.com/connectors/azure-app-service-web-apps-and-functions)

Browse

- [All Developer & infrastructure connectors](https://actionlake.com/connectors/category/developer-and-infrastructure)
- [All connectors](https://actionlake.com/connectors)
- [How actionlake compares](https://actionlake.com/compare)

actionlake is independent. It is not made or endorsed by Google Cloud Run; the name is the vendor's own. Counts are from the Google Cloud Run service file, version 1.0.0.

## Give your agent Google Cloud Run today.

[Connect Google Cloud Run free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing)

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.

---

Source: https://actionlake.com/connectors/google-cloud-run
More: https://actionlake.com/llms.txt
