s3

MCP server from tech4life87/s3-mcp-server

Installation

Run this command in your terminal to add the MCP server to Claude Code.

Run in terminal:

Command

claude mcp add --transport stdio tech4life87-s3-mcp-server node server.js \
  --env S3_BUCKET="Name of the S3 bucket the MCP server will interact with" \
  --env AWS_REGION="us-east-1 (or your region)" \
  --env AWS_ACCESS_KEY_ID="Your AWS access key ID" \
  --env AWS_SECRET_ACCESS_KEY="Your AWS secret access key"

How to use

The s3 MCP server is designed to bridge MCP tooling with Amazon S3. It allows you to perform S3-related MCP operations through the standard MCP interface, enabling commands that read from, write to, or list objects in a configured S3 bucket. Typical workflows involve configuring AWS credentials and the target S3 bucket, then invoking MCP commands supported by the server to manage objects, prefixes, and bucket metadata. The server translates MCP requests into S3 API calls and returns results in MCP-compatible responses, making it possible to incorporate S3 storage into your automated MCP pipelines.

To use the server, ensure you have Node.js installed and start the server with the provided entry point. Once running, connect your MCP client to the server’s endpoint and issue commands as defined by your MCP client’s capabilities. Common tasks include uploading objects, downloading objects, listing bucket contents, and managing object metadata through the MCP command set implemented by this server.

How to install

Prerequisites:

Node.js (LTS version) installed on your machine
AWS credentials with permissions to access the target S3 bucket
Network access to AWS S3 (public internet or VPC endpoints as configured)

Installation steps:

Clone the repository or download the release package
Install dependencies: npm install
Create and configure environment variables for AWS access and bucket:
- AWS_ACCESS_KEY_ID=your-access-key-id
- AWS_SECRET_ACCESS_KEY=your-secret-access-key
- AWS_REGION=your-aws-region
- S3_BUCKET=your-bucket-name
Start the MCP server: npm start
Verify the server is running by checking the log output and attempting a basic MCP command against the running endpoint.

Additional notes

Notes and tips:

Ensure the AWS credentials have least-privilege access to the required S3 bucket and actions you intend to perform.
If the server requires a specific AWS endpoint or VPC configuration, adjust AWS_REGION or endpoint settings accordingly in your environment.
Manage secrets securely; avoid hard-coding credentials in source files.
If you encounter connection issues, verify network egress to AWS S3 and confirm the bucket name matches the configured S3_BUCKET value.
Review any MCP-specific command mappings in the server code to understand supported operations (upload, download, list, delete, etc.).