s3-mcp-connector
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@s3-mcp-connectorlist objects in bucket my-bucket"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
๐ชฃ s3-mcp-connector
Talk to Amazon S3 โ or LocalStack, MinIO, any S3-compatible store โ from an MCP-speaking agent.
A single static Go binary that speaks the Model Context Protocol and exposes 8 tools for working with S3: list buckets, list/read/write/delete objects, create/delete buckets. Point it at real AWS or at a local LocalStack/MinIO instance with one environment variable โ same binary, same tools, zero code changes.
No Python, no uv, no runtime dependency to install โ just a binary and
an .mcp.json.
โจ Why this exists
An agent that can only talk about your S3 buckets isn't that useful. This gives it hands: it can look inside a bucket, read a config file out of it, drop a report back in, or clean up a stale prefix โ safely, with guardrails on size and destructive actions built in.
Related MCP server: S3 MCP Server
๐งฐ Tools
Tool | What it does | Write? |
| List buckets visible to the credentials | |
| List objects in a bucket, optional prefix, paginated | |
| Object metadata (size, type, ETag) without downloading | |
| Read an object's content โ text or base64, size-capped | |
| Write a small text/base64 object (โค 5 MB) | โ๏ธ |
| Delete one object | ๐๏ธ destructive |
| Create a bucket | โ๏ธ |
| Delete an empty bucket | ๐๏ธ destructive |
Every tool accepts an optional response_format: markdown (default,
pretty tables for a chat UI) or json (for programmatic use).
s3_get_object auto-detects text vs. binary content and caps output at
200,000 bytes by default (raise via max_bytes, hard cap
5,000,000) โ it's built for reading configs, logs, and small data
files, not bulk transfer. Reach for the AWS CLI or SDK directly for large
objects.
๐ Quickstart
Fastest path: grab a prebuilt bundle from the latest release โ
download s3-mcp-connector-plugin-<version>-<os>-<arch>.zip, unzip it,
and point Cowork/Claude at the plugin/ folder inside (see step 4 of
SETUP.md). No Go toolchain required.
From source:
# 1. Build
cd go-server
go mod tidy
go build -o s3-connector-server .
cp s3-connector-server ../plugin/servers/go/
# 2. Spin up LocalStack to test against (no AWS account needed)
cd ..
docker compose up -d
# 3. Point the connector at it
export AWS_ACCESS_KEY_ID=test
export AWS_SECRET_ACCESS_KEY=test
export AWS_REGION=us-east-1
export S3_ENDPOINT_URL=http://localhost:4566
export S3_FORCE_PATH_STYLE=true
./go-server/s3-connector-server # serves MCP over stdioOr make build && make localstack-up โ see the Makefile for
every shortcut (test, vet, fmt, lint, tidy, localstack-down).
Full walkthrough โ including wiring this up as a Claude/Cowork plugin and switching from LocalStack to real AWS โ is in SETUP.md.
๐ Configuration
Everything is environment variables, passed through by the plugin's
.mcp.json:
Variable | Purpose | Default |
| AWS credentials. Any non-empty values work against LocalStack. | โ |
| Region to use. |
|
| Custom endpoint. Leave unset for real AWS. | (unset) |
|
|
|
๐งช Quality bar
This isn't a toy script โ it's got the same checks you'd expect from a production Go service:
โ Unit tests for every input-validation path (
go test ./...)โ
go vet+gofmtcleanโ golangci-lint (govet, staticcheck, errcheck, gosec, and more)
โ govulncheck โ no known vulnerabilities in the dependency graph
โ CodeQL static security analysis on every push
โ End-to-end verified against real LocalStack โ every tool (create/delete bucket, put/get/head/list/delete object, and the 404 error path) was exercised against a live S3-compatible service, not mocks
โ Dependabot keeps Go modules and Actions current
All of it runs in CI on every push and PR.
๐ท๏ธ Releases & versioning
Versions follow semver and are cut automatically by
release-please from
Conventional Commits on main:
fix: ...โ patch (v0.1.0โv0.1.1)feat: ...โ minor (v0.1.1โv0.2.0)feat!: .../BREAKING CHANGE:footer โ major (v0.2.0โv1.0.0)
Every merged PR updates a standing "chore(main): release vX.Y.Z" PR with an auto-generated CHANGELOG.md. Merging that PR:
tags the release and publishes it on GitHub
builds and attaches zipped, ready-to-install plugin bundles for linux/darwin/windows ร amd64/arm64
regenerates
server.jsonfrom those exact assets (fresh version + SHA-256 hashes) and publishes it to the official MCP Registry viamcp-publisher, authenticated with GitHub OIDC โ no stored secrets
See .github/workflows/release-please.yml
and .github/workflows/publish-mcp-registry.yml
(also runnable by hand for an existing tag via workflow_dispatch).
๐ Layout
s3-mcp-connector/
โโโ README.md โ you are here
โโโ SETUP.md โ step-by-step setup guide (LocalStack + real AWS)
โโโ CONTRIBUTING.md โ how to contribute
โโโ CODE_OF_CONDUCT.md
โโโ SECURITY.md โ vulnerability reporting
โโโ CODEOWNERS
โโโ LICENSE โ MIT
โโโ Makefile โ build / test / lint / localstack shortcuts
โโโ docker-compose.yml โ LocalStack, for local testing
โโโ .golangci.yml โ lint rules
โโโ release-please-config.json โ semver/changelog automation config
โโโ .release-please-manifest.json
โโโ server.json โ MCP Registry manifest (regenerated fresh per release by CI)
โโโ scripts/
โ โโโ render-server-json.sh โ rebuilds server.json from a release's zip assets
โโโ .github/
โ โโโ workflows/
โ โ โโโ ci.yml โ build, vet, test, lint, govulncheck
โ โ โโโ codeql.yml โ security scanning
โ โ โโโ pr-title.yml โ Conventional Commits PR title check
โ โ โโโ release-please.yml โ version PRs, tagging, GitHub releases
โ โ โโโ publish-mcp-registry.yml โ publishes server.json to the MCP Registry
โ โ โโโ rebuild-release-assets.yml โ manual re-attach fallback
โ โโโ ISSUE_TEMPLATE/
โ โโโ PULL_REQUEST_TEMPLATE.md
โ โโโ dependabot.yml
โโโ go-server/ โ the MCP server source
โ โโโ main.go
โ โโโ main_test.go
โ โโโ go.mod / go.sum
โ โโโ README.md
โโโ plugin/ โ installable Cowork/Claude plugin
โโโ .claude-plugin/plugin.json
โโโ .mcp.json โ holds credentials locally โ never commit real ones
โโโ servers/go/ โ compiled binary goes here๐ค Contributing
PRs and issues are very welcome โ see CONTRIBUTING.md for the full guide (setup, coding conventions, how to add a new tool) and the Code of Conduct.
main is protected: every change, including the maintainer's, lands via
pull request with CI green. PR titles must follow
Conventional Commits โ that's what
drives the automatic versioning above.
Found a security issue? Please follow SECURITY.md instead of opening a public issue.
๐ License
MIT ยฉ Ferhat Dundar
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- FlicenseBqualityDmaintenanceEnables AI models to interact with Akave's S3-compatible storage by providing tools for managing storage buckets and objects through standardized Model Context Protocol (MCP).Last updated13973
- AlicenseAqualityDmaintenanceEnables interaction with S3-compatible storage services like AWS S3 and Cloudflare R2, supporting bucket management, object listing, reading, uploading, and deletion operations.Last updated5252ISC
- Alicense-qualityFmaintenanceEnables interaction with AWS S3 through MCP, supporting bucket and object management, lifecycle configurations, tagging, policies, CORS settings, presigned URLs, and file uploads/downloads.Last updated3MIT
- FlicenseAqualityDmaintenanceProvides tools for interacting with MinIO and S3-compatible object storage through MCP clients like Claude. It enables comprehensive bucket and object management, including listing, creating, uploading, and generating presigned URLs.Last updated132
Related MCP Connectors
Shared long-term memory vault for AI agents with 20 MCP tools.
OCR, transcription, file extraction, and image generation for AI agents via MCP.
Real-time Amazon, WIPO & PACER data for AI agents โ 19 tools via the MCP protocol.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/FerhatDundar/s3-mcp-connector'
If you have feedback or need assistance with the MCP directory API, please join our Discord server