Google Cloud Functions integration
Google Cloud Functions serverless compute API. Deploy single-purpose, event-driven functions that automatically scale. Supports HTTP triggers, Pub/Sub events, Cloud Storage events, and more.
Say what should happen.
The workflow builds itself.
Common Google Cloud Functions use cases
- automate function management
- automate operation management
- automate iam policy management
- get function programmatically
- list runtime programmatically
- call function programmatically
- get operation programmatically
- list function programmatically
- list location programmatically
- get iam policy programmatically
What you can do with Google Cloud Functions
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.
Function, 6 operations
call_functionCall functionPOSTSynchronously invoke a deployed Cloud Function and return its response. This is the legacy v1 endpoint - it requires using the full absolute URL `https://cloudfunctions.googleapis.com/v1/projects/{project}/locations/{location}/functions/{function}...create_functionCreate functionPOSTCreate a new Cloud Function in a project and location. Requires a function body with runtime, entry point, and source code. Returns a long-running operation.delete_functionDelete functionDELETEDelete a Cloud Function. Returns a long-running operation that resolves once the function is permanently removed.get_functionGet functionGETGet the details of a specific Cloud Function including its configuration, state, source code location, and runtime settings.list_functionsList functionsGETList all Cloud Functions in a project and location. Supports pagination and filtering by name or labels. Returns a paginated list of Function resources.update_functionUpdate functionPATCHUpdate an existing Cloud Function's configuration. Use updateMask to specify which fields to change. Returns a long-running operation.
Iam policy, 2 operations
get_iam_policyGet iam policyGETGet the IAM access control policy for a Cloud Function. Returns policy bindings that map roles to members allowed to invoke or manage the function.set_iam_policySet iam policyPOSTSet the IAM access control policy for a Cloud Function, replacing any existing policy. Use to grant or revoke invoker or admin roles on the function.
Operation, 2 operations
get_operationGet operationGETGet the latest state of a long-running operation. Poll this endpoint to check whether a create, update, or delete function operation has completed.list_operationsList operationsGETList long-running operations for Cloud Functions in a project and location. Use to track the status of create, update, or delete operations.
Generate download url, 1 operation
generate_download_urlGenerate download urlPOSTGenerate a signed URL to download the source code of a deployed Cloud Function. Useful for inspecting or backing up deployed function source.
Generate upload url, 1 operation
generate_upload_urlGenerate upload urlPOSTGenerate a signed URL for uploading function source code to Cloud Storage. The uploaded zip file can then be referenced during function creation or update.
Iam permission, 1 operation
test_iam_permissionsTest iam permissionsPOSTTest which IAM permissions the caller has on a Cloud Function. Useful for checking whether a service account can invoke or manage a specific function.
Location, 1 operation
list_locationsList locationsGETList all Google Cloud regions where Cloud Functions is available for a project. Returns location IDs, display names, and metadata.
Runtime, 1 operation
list_runtimesList runtimesGETList all available runtimes supported by Cloud Functions in a given location. Returns runtime identifiers, display names, and their lifecycle stages (e.g., ACTIVE, DEPRECATED).
OAuth scopes Google Cloud Functions requires
Each operation declares the scopes Google Cloud Functions requires for it.
https://www.googleapis.com/auth/cloud-platformneeded by call_function, create_function, delete_function and 12 more
Use Google Cloud Functions from Claude Code, Cursor or Codex
Connect Google Cloud Functions in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Google Cloud Functions operations become tools the client can call, next to every other integration you connected.
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"
[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"{
"mcpServers": {
"livecontext": {
"type": "http",
"url": "https://livecontext.ai/mcp",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}How to connect Google Cloud Functions
- Create your workspace
Sign up free. Nothing to install.
- Connect Google Cloud Functions once
Add your Google Cloud Functions 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 Functions integration FAQ
What can you do with the Google Cloud Functions integration?
LiveContext exposes 15 operations on Google Cloud Functions, covering function, iam policy, operation and generate download url. Common uses include automate function management, automate operation management and automate iam policy management.
Which OAuth scopes does Google Cloud Functions require?
The operations that declare a scope all need https://www.googleapis.com/auth/cloud-platform.
