Server facts
aws-s3-mcp
Project
- Author
- samuraikun
- Repository
- github.com/samuraikun/aws-s3-mcp
- License
- MIT
- Category
- Cloud & DevOps
Tech
- Runtime / language
- node
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 30
- Last commit
- Data as of
Tags
- Aws
- Mcp Servers
- Typescript
- aws s3
- mcp
- modelcontextprotocol
Overview
Bucket selection comes first in the aws-s3-mcp workflow: list-buckets returns the S3 buckets the server can access, subject to its configured allowlist. From there, list-objects browses a bucket with prefix filtering, and get-object retrieves the selected object's contents with text and binary support. These tools let an LLM client move from discovering storage locations to reading stored data. Configuration covers the AWS region, permitted bucket names, and a limit on how many buckets a listing returns.
For Claude Desktop, the connection uses STDIO; the project's default HTTP mode serves web clients and includes Server-Sent Events. Developers can run the Node.js server locally or deploy it with Docker. The Docker Compose setup also includes MinIO for local testing, creating test buckets and adding sample files. MCP Inspector provides a testing and debugging interface for the documented transport and deployment options, including local processes, Docker with AWS, and Docker Compose with MinIO.
aws-s3-mcp setup notes
- aws-s3-mcp records stdio only; confirm a network transport upstream before planning remote access.