S3 Mcp

Created By
ashgwa year ago
Fully Loaded AWS S3 Model Context Protocol Server (MCP)
Overview

What is S3 Mcp?

S3 Mcp is a fully loaded AWS S3 Model Context Protocol Server that allows users to manage S3 buckets and objects efficiently.

How to use S3 Mcp?

To use S3 Mcp, you can run it via Docker or integrate it with Cursor MCP configuration. Set your AWS credentials as environment variables and execute the server commands as specified in the documentation.

Key features of S3 Mcp?

  • Manage S3 buckets and objects
  • Handle lifecycle configurations
  • Set and retrieve object tags
  • Manage bucket policies
  • Configure CORS settings
  • Generate presigned URLs for object access

Use cases of S3 Mcp?

  1. Creating and managing S3 buckets for data storage.
  2. Uploading and retrieving files from S3 buckets.
  3. Setting up lifecycle rules for automatic data management.
  4. Configuring CORS for web applications accessing S3 resources.

FAQ from S3 Mcp?

  • Is S3 Mcp free to use?

Yes! S3 Mcp is open-source and free to use.

  • What are the prerequisites for using S3 Mcp?

You need to have Docker installed and valid AWS credentials to access S3 services.

  • Can I run S3 Mcp on my local machine?

Yes! You can run S3 Mcp locally using Docker.

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

Recommend Servers

View All
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.

8 hours ago