Integration

Google Cloud Storage integration

Google Cloud Storage for secure and scalable object storage. Store and retrieve data of any size with global availability, fine-grained access control, and seamless integration with Google Cloud services. Essential for building applications requiring reliable cloud storage, data analytics, and content delivery.

Connect Google Cloud Storage How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Google Cloud Storage.Built from the 13 Google Cloud Storage tools below, on the connection you add once.

Common Google Cloud Storage use cases

Cleaning up temporary files and expired content
Creating backup copies across buckets or regions
Assembling large files uploaded in parallel chunks
Inspecting bucket configuration for troubleshooting
Cleaning up temporary or test buckets after projects
Downloading user files and media in web applications
Browsing HNS bucket folder structures in file managers
Auditing bucket access permissions for security compliance
Uploading user-generated content like images and documents
Provisioning storage for new applications or data pipelines

What you can do with Google Cloud Storage

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.

Object, 7 operations

compose_objectsCompose objectsPOSTCombines multiple source objects into a single destination object.
copy_objectCopy objectPOSTCreates a copy of an object within Cloud Storage or across buckets.
delete_objectDelete objectDELETEPermanently removes an object from a Cloud Storage bucket.
download_objectDownload objectGETDownloads the complete binary or text content of a Cloud Storage object.
get_object_metadataGet object metadataGETRetrieves comprehensive metadata for a Cloud Storage object without downloading content.
list_objectsList objectsGETRetrieves a paginated list of objects stored in a Cloud Storage bucket.
upload_objectUpload objectPOSTUploads a new object or replaces an existing object in Cloud Storage.

Bucket, 5 operations

create_bucketCreate bucketPOSTCreates a new Cloud Storage bucket with specified configuration in a GCP project.
delete_bucketDelete bucketDELETEPermanently removes an empty Cloud Storage bucket from the GCP project.
get_bucketGet bucketGETRetrieves detailed metadata and configuration for a specific Cloud Storage bucket.
get_bucket_iam_policyGet bucket iam policyGETRetrieves the IAM policy configuration for a Cloud Storage bucket.
list_bucketsList bucketsGETRetrieves a list of all Cloud Storage buckets within a GCP project.

Folder, 1 operation

list_foldersList foldersGETLists folders within a Cloud Storage bucket that has hierarchical namespace (HNS) enabled.

OAuth scopes Google Cloud Storage requires

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

https://www.googleapis.com/auth/devstorage.full_controlneeded by compose_objects, copy_object, create_bucket and 10 more

Google Cloud Storage API rate limits

1,000 requests per second

Per-bucket initial baseline (verified 2026-05-28 on docs.cloud.google.com/storage/quotas): ~1,000 object writes/sec and ~5,000 object reads/sec, auto-scaling beyond. Batch JSON API requests cap at 100 calls and <10 MiB total.

These are the limits Google Cloud Storage documents, not ones LiveContext measured. They can change and often depend on your plan, so check the Google Cloud Storage documentation for current values.

Use Google Cloud Storage from Claude Code, Cursor or Codex

Connect Google Cloud Storage in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Google Cloud Storage 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 Storage

Create your workspace
Sign up free. Nothing to install.
Connect Google Cloud Storage once
Add your Google Cloud Storage 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 Storage integration FAQ

What can you do with the Google Cloud Storage integration?

LiveContext exposes 13 operations on Google Cloud Storage, covering object, bucket and folder. Common uses include Cleaning up temporary files and expired content, Creating backup copies across buckets or regions and Assembling large files uploaded in parallel chunks.

Which OAuth scopes does Google Cloud Storage require?

The operations that declare a scope all need https://www.googleapis.com/auth/devstorage.full_control.

What are the Google Cloud Storage API rate limits?

Google Cloud Storage documents 1,000 requests per second. Per-bucket initial baseline (verified 2026-05-28 on docs.cloud.google.com/storage/quotas): ~1,000 object writes/sec and ~5,000 object reads/sec, auto-scaling beyond. Batch JSON API requests cap at 100 calls and <10 MiB total. Limits are set by Google Cloud Storage and can depend on your plan.