Cloud Storage MCP Server

Created By
gitskyfluxa year ago
MCP Server to interact with Google Cloud Storage
Overview

What is Cloud Storage MCP Server?

Cloud Storage MCP Server is a Model Context Protocol (MCP) server designed to facilitate interactions with Google Cloud Storage, allowing users to manage their storage buckets and files efficiently.

How to use Cloud Storage MCP Server?

To use the Cloud Storage MCP Server, you need to install the necessary dependencies, build the project, and configure it with your Google Cloud project details. After setup, you can use various commands to interact with your Cloud Storage.

Key features of Cloud Storage MCP Server?

  • List Cloud Storage buckets in a project
  • Get details of a specific bucket
  • List files in a bucket
  • Get details of a specific file
  • Upload files to a bucket
  • Download files from a bucket
  • Delete files from a bucket

Use cases of Cloud Storage MCP Server?

  1. Managing multiple Google Cloud Storage buckets.
  2. Automating file uploads and downloads in cloud storage.
  3. Monitoring and retrieving file details for data analysis.

FAQ from Cloud Storage MCP Server?

  • What programming language is used for this project?

The project is developed in JavaScript.

  • Is there a license for this project?

Yes, it is licensed under the MIT license.

  • How can I contribute to the project?

You can contribute by submitting issues or pull requests on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
gitskyflux
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

9 hours ago
Alloy

2 days ago