How do I install S3 MCP Connector?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does S3 MCP Connector need an API key?

The publisher lists these environment variables: AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_REGION, S3_ENDPOINT_URL, S3_FORCE_PATH_STYLE.

What transport does S3 MCP Connector use?

S3 MCP Connector runs locally over stdio.

When was S3 MCP Connector last checked?

Last checked 2026-11-09. MCP server for Amazon S3 and S3-compatible endpoints (LocalStack, MinIO). Single Go binary.

S3 MCP Connector MCP server

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

mcpb https://github.com/FerhatDundar/s3-mcp-connector/releases/download/v0.2.0/s3-mcp-connector-plugin-v0.2.0-darwin-arm64.zip

Credentials from the publisher

AWS_ACCESS_KEY_ID — AWS access key ID
AWS_SECRET_ACCESS_KEY — AWS secret access key
AWS_REGION — AWS region (default us-east-1)
S3_ENDPOINT_URL — Custom S3 endpoint, e.g. http://localhost:4566 for LocalStack. Leave unset for real AWS.
S3_FORCE_PATH_STYLE — Set to true for LocalStack/MinIO path-style addressing.

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1AWS_ACCESS_KEY_ID=<secret> AWS_SECRET_ACCESS_KEY=<secret> AWS_REGION=<value> S3_ENDPOINT_URL=<value> S3_FORCE_PATH_STYLE=<value> claude mcp add io.github.ferhatdundar-s3-mcp-connector -- mcpb https://github.com/FerhatDundar/s3-mcp-connector/releases/download/v0.2.0/s3-mcp-connector-plugin-v0.2.0-darwin-arm64.zip

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.ferhatdundar-s3-mcp-connector": {4      "command": "mcpb",5      "args": [6        "https://github.com/FerhatDundar/s3-mcp-connector/releases/download/v0.2.0/s3-mcp-connector-plugin-v0.2.0-darwin-arm64.zip"7      ],8      "env": {9        "AWS_ACCESS_KEY_ID": "<secret>",10        "AWS_SECRET_ACCESS_KEY": "<secret>",11        "AWS_REGION": "<value>",12        "S3_ENDPOINT_URL": "<value>",13        "S3_FORCE_PATH_STYLE": "<value>"14      }15    }16  }17}

claude_desktop_config.json

Local · mcpbPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

🪣 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.

🧰 Tools

Tool	What it does	Write?
`s3_list_buckets`	List buckets visible to the credentials
`s3_list_objects`	List objects in a bucket, optional prefix, paginated
`s3_head_object`	Object metadata (size, type, ETag) without downloading
`s3_get_object`	Read an object's content — text or base64, size-capped
`s3_put_object`	Write a small text/base64 object (≤ 5 MB)	✍️
`s3_delete_object`	Delete one object	🗑️ destructive
`s3_create_bucket`	Create a bucket	✍️
`s3_delete_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 stdio

Or 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_ACCESS_KEY_ID` / `AWS_SECRET_ACCESS_KEY`	AWS credentials. Any non-empty values work against LocalStack.	—
`AWS_REGION`	Region to use.	`us-east-1`
`S3_ENDPOINT_URL`	Custom endpoint. Leave unset for real AWS.	(unset)
`S3_FORCE_PATH_STYLE`	`true` for LocalStack/MinIO (path-style addressing).	`false`

🧪 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 + gofmt clean
✅ 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.json from those exact assets (fresh version + SHA-256 hashes) and publishes it to the official MCP Registry via mcp-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.

S3 MCP Connector