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
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

32 minutes ago