Local server or remote?

Both are official. The local stdio server (`npx @google-cloud/storage-mcp`) is best for personal automation and Gemini CLI; the remote endpoint at `storage.googleapis.com/storage/mcp` is fully managed by Google with IAM-based auth and is the right choice for production agents. The remote server is the one announced on 2026-06-03.

How does authentication work?

The remote MCP uses OAuth 2.0 tied to IAM, so the agent inherits the caller's GCS permissions and every action lands in Cloud Audit Logs. The local server uses Application Default Credentials — typically a `gcloud auth application-default login` session or a service-account key, with the same IAM enforcement.

Can it delete buckets or overwrite objects?

Yes, but the destructive tools (delete bucket, delete object, overwrite object, modify metadata) are an opt-in tier. The safe tools (list buckets, read objects, create new buckets and objects, run Storage Insights queries) are on by default.

Is it ready for production?

The remote server is generally available; the local package is at version 0.6.0 and labelled as in preview in the README. Treat the local install as preview-grade and the remote endpoint as production-grade until the local package crosses 1.0.

Google Cloud Storage

Name: Top MCPs — curated MCP directory
Creator: Top MCPs
License: https://creativecommons.org/licenses/by/4.0/

Official

Read, write, and manage GCS buckets and objects from an AI agent — official Google MCP, local or remote.

Score 86(?)GoogleApache-2.0 843Verified Jun 15, 2026Top MCPs for Filesystem & Storage →

Install View on GitHub

Quick answer

What it does

Exposes Google Cloud Storage operations as MCP tools — list/create buckets, read/write/delete objects, fetch object and bucket metadata, run Storage Insights BigQuery queries — with a split between safe (read + create) and destructive (delete + overwrite) tools so the destructive tier can be turned off.

Best for

Reading GCS objects as agent context
Writing generated artifacts to a bucket
Bucket and object metadata audits
Storage Insights cost/lifecycle reports

Not for

Non-GCS object stores (S3, R2, Azure Blob)
Unattended destructive operations on production buckets

Setup recipe

Pick your client, then follow the three steps.

Install

claude_desktop_config.jsonjson

{
  "mcpServers": {
    "google-cloud-storage": {
      "command": "npx",
      "args": [
        "-y",
        "@google-cloud/storage-mcp"
      ]
    }
  }
}

Paste under mcpServers. Fully quit and reopen Claude after editing.

CLI or .mcp.jsonshell

claude mcp add google-cloud-storage -- npx -y @google-cloud/storage-mcp

Run from your repo. Commit .mcp.json to share with your team.

.cursor/mcp.jsonjson

{
  "mcpServers": {
    "google-cloud-storage": {
      "command": "npx",
      "args": [
        "-y",
        "@google-cloud/storage-mcp"
      ]
    }
  }
}

Global path: ~/.cursor/mcp.json. Reload window after editing.

.vscode/mcp.jsonjsonc

{
  "servers": {
    "google-cloud-storage": {
      "command": "npx",
      "args": [
        "-y",
        "@google-cloud/storage-mcp"
      ]
    }
  }
}

VS Code uses the "servers" key (not "mcpServers").

~/.codeium/windsurf/mcp_config.jsonjson

{
  "mcpServers": {
    "google-cloud-storage": {
      "command": "npx",
      "args": [
        "-y",
        "@google-cloud/storage-mcp"
      ]
    }
  }
}

Open via Cascade → hammer icon → Configure.

cline_mcp_settings.jsonjson

{
  "mcpServers": {
    "google-cloud-storage": {
      "command": "npx",
      "args": [
        "-y",
        "@google-cloud/storage-mcp"
      ]
    }
  }
}

Open via the Cline sidebar → MCP Servers → Edit.

~/.continue/config.jsonjson

{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "@google-cloud/storage-mcp"
          ]
        }
      }
    ]
  }
}

Continue uses modelContextProtocolServers with a transport block.

~/.codex/config.tomlshell

# ~/.codex/config.toml
[mcp_servers.google-cloud-storage]
command = "npx"
args = [
  "-y",
  "@google-cloud/storage-mcp",
]

Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

~/.config/zed/settings.jsonjsonc

{
  "context_servers": {
    "google-cloud-storage": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "@google-cloud/storage-mcp"
        ]
      }
    }
  }
}

Zed calls them "context_servers". Settings live-reload on save.

ChatGPT → Settings → Connectors (remote URL)json

{
  "name": "Google Cloud Storage",
  "transport": "http",
  "url": "https://storage.googleapis.com/storage/mcp"
}

Paste this into Settings → Connectors → Add custom connector. Requires ChatGPT Pro / Team / Enterprise / Edu with Developer mode enabled. ChatGPT supports remote HTTPS MCP servers only — stdio servers must be hosted on a public HTTPS endpoint first.

2
Set required secrets
No credentials required — this MCP runs over stdio without authentication.
3
Try a minimum working prompt
Audit objects written in the last 24 hours
Using the GCS MCP, list every object created in `gs://my-prod-bucket` in the last 24 hours. Return object name, size, content type, and the service account that wrote it.
Tested with: Claude Desktop, Cursor, Gemini CLI.

Tools & permissions

Tools list pending verification. The server exposes tools over MCP; we haven’t yet parsed its capability manifest into this page. Check the GitHub repo for the authoritative list.

Security & scope

Access scope: Read + write
Sandbox: Authenticates with Google Cloud IAM — the agent can only act on buckets and objects the calling identity has permission for. Every call to the remote MCP lands in Cloud Audit Logs. Destructive tools are an opt-in tier.
Gotchas: The destructive tier (delete, overwrite, modify metadata) runs without a confirmation step once enabled — scope the IAM identity to least privilege or leave destructive tools off.
The local package is labelled as in preview at 0.6.0; production agents should prefer the managed remote endpoint.

Agent prompt pack

— copy into Claude, Cursor, or ChatGPT.

Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.

Recommend the best MCP servers for [task: e.g. filesystem & storage work] in [client: Claude].

Constraints:
- Prefer tools that are [official | open-source | read-only] — pick what matters for my use case.
- Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport].
- Return at most 3 picks, ranked.

For each pick include:
1. One-sentence rationale.
2. The ready-to-paste install snippet for my client.
3. Any required secrets I need to create before installing.

Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-filesystem-storage

Compare Google Cloud Storage against a real alternative. Swap the second MCP in [brackets] if you want a different match.

Compare Google Cloud Storage MCP vs [Cloudflare MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"].

Judge them on:
- Setup time and complexity (what a new user hits first).
- Auth model (none / API key / OAuth 2.1) and credential risk.
- Transport (stdio / Streamable HTTP / SSE) and where the server runs.
- Required secrets and the blast radius if they leak.
- Operational risk in an unattended agent loop.
- Which one is "good enough" for a weekend prototype vs. production.

End with one sentence: which should I pick for my scenario, which is: [my scenario].

References:
- https://top-mcps.com/mcp/google-cloud-storage
- top-mcps.com listing for Cloudflare

Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.

Install the Google Cloud Storage MCP server for my [client: Claude] at the default config path for that client.

Use the exact install snippet published at https://top-mcps.com/mcp/google-cloud-storage (fetch https://top-mcps.com/mcp/google-cloud-storage.json for the canonical server.json if you can read URLs).

Before finishing:
1. Create the required secrets (no secrets) and put them in the appropriate env block — do not hard-code them.
2. Restart or reload the client so it picks up the new server.
3. Verify the server is connected (green / running state) and at least one tool is listed.
4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry.

Confirm when done and list the tools the server now exposes.

Frequently asked questions

What changed

— 2 updates tracked.

Jun 15, 2026
Refreshed install snippets and fact sheet; verified for 2026.
Jun 3, 2026
Initial directory listing.

More Filesystem & Storage MCPs

Other tools in the same category worth evaluating.

Filesystem

Official

Read and write local files with configurable access controls.

filesystemfilesreadwrite

2 minLow

Notion

Official

Read, write, and search across Notion pages, databases, and blocks.

notiondocsdatabasesknowledge

5 minLow

Cloudflare

Official

Manage Workers, R2 buckets, DNS, and edge policies on Cloudflare.

cloudflareedgeworkersdns

10 minMedium

Compared with Google Cloud Storage

Side-by-side breakdowns for the choices people most often weigh against this MCP.

Google Cloud StoragevsCloudflare Google Cloud StoragevsBox Google Cloud StoragevsOneDrive & SharePoint Google Cloud StoragevsFilesystem

Exploring Top MCPs for Filesystem & Storage? See all Filesystem & Storage MCPs →

Quick answer

What it does

Best for

Not for

Setup recipe

Install

Set required secrets

Try a minimum working prompt

Tools & permissions

Security & scope

Agent prompt pack

Full details

Frequently asked questions

Local server or remote?

How does authentication work?

Can it delete buckets or overwrite objects?

Is it ready for production?

What changed

More Filesystem & Storage MCPs

Filesystem

Notion

Cloudflare

Compared with Google Cloud Storage