What can you do with the Google Cloud Run integration?

LiveContext exposes 22 operations on Google Cloud Run, covering cancel execution, create job, create service and delete job. Common uses include execute get job programmatically, execute run job programmatically and execute list job programmatically.

Which OAuth scopes does Google Cloud Run require?

The operations that declare a scope all need https://www.googleapis.com/auth/cloud-platform.

LiveContext

All integrations

Google Cloud Run integration

Google Cloud Run serverless container platform API. Deploy, manage, and scale containerized applications with automatic HTTPS, custom domains, and integration with Google Cloud services.

22 toolsOAuthAPI docs

Connect Google Cloud Run How integrations work

Common Google Cloud Run use cases

execute get job programmatically
execute run job programmatically
execute list job programmatically
execute create job programmatically
execute delete job programmatically
execute update job programmatically
execute get service programmatically
execute get revision programmatically
execute list service programmatically
execute get execution programmatically

What you can do with Google Cloud Run

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Cancel execution, 1 operation

POSTcancel_execution
Cancels a running Cloud Run job execution and all its running tasks.

Create job, 1 operation

POSTcreate_job
Creates a new Cloud Run job in the specified project and location.

Create service, 1 operation

POSTcreate_service
Creates a new Cloud Run service in the specified project and location.

Delete job, 1 operation

DELETEdelete_job
Deletes a Cloud Run job and all its associated executions.

Delete revision, 1 operation

DELETEdelete_revision
Deletes a specific Cloud Run service revision. Active revisions serving traffic cannot be deleted.

Delete service, 1 operation

DELETEdelete_service
Deletes a Cloud Run service and all its associated revisions.

Get execution, 1 operation

GETget_execution
Retrieves the details and status of a specific Cloud Run job execution.

Get iam policy, 1 operation

GETget_iam_policy
Gets the IAM access control policy for a Cloud Run service.

Get job, 1 operation

GETget_job
Retrieves the details of a specific Cloud Run job.

Get operation, 1 operation

GETget_operation
Retrieves the latest state of a long-running Cloud Run operation.

Get revision, 1 operation

GETget_revision
Retrieves the details of a specific Cloud Run service revision.

Get service, 1 operation

GETget_service
Retrieves the details of a specific Cloud Run service.

List execution, 1 operation

GETlist_executions
Lists all executions for a Cloud Run job, ordered by creation time descending.

List job, 1 operation

GETlist_jobs
Lists all Cloud Run jobs in the specified project and location.

List operation, 1 operation

GETlist_operations
Lists long-running operations for Cloud Run resources in the specified project and location.

List revision, 1 operation

GETlist_revisions
Lists all revisions for a Cloud Run service, ordered by creation time descending.

List service, 1 operation

GETlist_services
Lists all Cloud Run services in the specified project and location.

Run job, 1 operation

POSTrun_job
Triggers a new execution of a Cloud Run job with the current job configuration.

Set iam policy, 1 operation

POSTset_iam_policy
Sets the IAM access control policy for a Cloud Run service, replacing any existing policy.

Test iam permission, 1 operation

POSTtest_iam_permissions
Tests whether the caller has the specified IAM permissions on a Cloud Run service.

Update job, 1 operation

PATCHupdate_job
Updates an existing Cloud Run job with new configuration.

Update service, 1 operation

PATCHupdate_service
Updates an existing Cloud Run service with new configuration.

OAuth scopes Google Cloud Run requires

Each operation declares the scopes Google Cloud Run requires for it.

https://www.googleapis.com/auth/cloud-platformneeded by cancel_execution, create_job, create_service and 19 more

Use Google Cloud Run from Claude Code, Cursor or Codex

Connect Google Cloud Run in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Google Cloud Run operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Google Cloud Run

Create your workspace
Sign up free. Nothing to install.
Connect Google Cloud Run once
Add your Google Cloud Run connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Google Cloud Run integration FAQ

What can you do with the Google Cloud Run integration?: LiveContext exposes 22 operations on Google Cloud Run, covering cancel execution, create job, create service and delete job. Common uses include execute get job programmatically, execute run job programmatically and execute list job programmatically.
Which OAuth scopes does Google Cloud Run require?: The operations that declare a scope all need https://www.googleapis.com/auth/cloud-platform.