Full read-write Claude connector for Google Cloud Storage

Let Claude upload, move, and manage objects in Google Cloud Storage

Stop running gsutil commands and clicking through the Cloud console to shuffle files between buckets. Claude lists, uploads, copies, and tidies objects right where the data already lives, and destructive actions wait for your approval.

Build my connector Talk to us

Google Cloud Storage is Google Cloud's object store for files, backups, data lakes, and static assets, organized into buckets. Teams want Claude to do more than describe what is in a bucket: to upload objects, move and copy them, and manage lifecycle and access.

What is a Google Cloud Storage MCP server?

A Google Cloud Storage MCP server is a small hosted service that exposes Google Cloud Storage's data and actions to Claude over the Model Context Protocol, so Claude can files and folders inside your own account. We build it as a custom connector with separate read and write tools, and destructive actions stay gated behind your approval.

What can Google Cloud Storage's current connector do today?

Google offers an official Cloud Storage connector for Claude, but it ships a fixed, standard tool set: create and list buckets, list and read objects, write object data, and read metadata. It covers a generic slice of what the API can do. A custom connector adds the full surface your workflow needs, copy and move, lifecycle and access management, custom metadata, scoping, and confirmation gates, shaped to how your team works.

What does full read-write Google Cloud Storage access unlock?

Full read-write Google Cloud Storage access lets Claude list and read objects, upload new ones, copy or move between buckets, set or remove object metadata, and manage lifecycle and access settings within your permissions. The bucket housekeeping and transfers that used to mean console clicks or gsutil commands happen where the data already lives.

Upload a file or generated artifact to a specific bucket and prefix
Copy or move objects between buckets or folders
List objects under a prefix and report sizes, classes, and last-modified dates
Set or remove custom metadata and content types on objects
Delete or archive objects after you approve the action
Apply or update a lifecycle rule on a bucket

Can Claude upload files to a Google Cloud Storage bucket?

Yes. Claude can upload a file or generated artifact to a specific bucket and prefix through a write tool, setting the content type and custom metadata you specify. The official connector can write object data, and a purpose-built MCP server adds the metadata control and bucket scoping your workflow needs.

Can Claude move and copy objects between buckets in Google Cloud Storage?

Yes. Claude can copy or move objects between buckets and prefixes, list what sits under a path, and report sizes, storage classes, and last-modified dates. Copy and move sit outside the official connector's standard tool set, so a custom connector adds them and turns bucket housekeeping into something Claude does directly.

Will Claude delete objects from Google Cloud Storage on its own?

No. Delete and archive are separate, gated actions in Google Cloud Storage. Claude can list candidates and propose what to remove, but objects are only deleted after you approve. The connector inherits only the IAM permissions of the credential you grant, so it never has more access than your account.

How a Google Cloud Storage connector works

We build a small MCP server that authenticates to Google Cloud Storage with a scoped service account or OAuth and the narrowest IAM permissions the work needs. Read tools (list, get object, read metadata) and write tools (upload, copy, set metadata) are separated, and destructive actions like delete or making objects public require your confirmation. Claude never has more access than the credential you grant, and we can restrict it to specific buckets or projects.

Frequently asked questions

Can Claude upload files to a Google Cloud Storage bucket?

Yes. A custom connector exposes an upload write tool, so Claude can put a file or generated artifact into a specific bucket and prefix, with the content type and metadata you specify. The official connector can write object data too, but a purpose-built MCP server adds the metadata control, scoping, and confirmation gates around it that your workflow needs.

Will Claude delete objects from my bucket on its own?

No. Delete is a separate, gated write action. Claude can list candidates and propose a deletion, but objects are only removed after you approve. You decide which actions run automatically and which require a confirmation step, and you can keep delete out of the connector entirely.

Can I limit the connector to certain buckets or projects?

Yes. The connector authenticates with a service account or OAuth credential you control, and it inherits only the IAM permissions that credential holds. You can scope it to specific buckets or a single project, and if your setup needs it we can add IP allowlisting so access only comes from approved addresses.

Related connectors

Amazon S3 connector Egnyte connector Azure Blob Storage connector

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us