S3 runs on your own machine — the client starts it, so there is no endpoint to ping. 54 installs a week from npm. Last commit 30 Aug 2026.
MCP server for AWS S3 with fine-grained tool control and S3-compatible endpoint support.
What the code does
We read the source, 4 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
этот файл ставится пользователю, но в репозитории его нет
const initProcess = spawn(this.claudeCodePath, args, {
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add s3 -e 'AWS_ACCESS_KEY_ID=<AWS_ACCESS_KEY_ID>' -e 'AWS_SECRET_ACCESS_KEY=<AWS_SECRET_ACCESS_KEY>' -- npx -y s3-aws-mcp-server{
"mcpServers": {
"s3": {
"command": "npx",
"args": [
"-y",
"s3-aws-mcp-server"
],
"env": {
"AWS_ACCESS_KEY_ID": "<AWS_ACCESS_KEY_ID>",
"AWS_SECRET_ACCESS_KEY": "<AWS_SECRET_ACCESS_KEY>"
}
}
}
}[mcp_servers.s3]
command = "npx"
args = ["-y", "s3-aws-mcp-server"]
env = { AWS_ACCESS_KEY_ID = "<AWS_ACCESS_KEY_ID>", AWS_SECRET_ACCESS_KEY = "<AWS_SECRET_ACCESS_KEY>" }{
"mcpServers": {
"s3": {
"command": "npx",
"args": [
"-y",
"s3-aws-mcp-server"
],
"env": {
"AWS_ACCESS_KEY_ID": "<AWS_ACCESS_KEY_ID>",
"AWS_SECRET_ACCESS_KEY": "<AWS_SECRET_ACCESS_KEY>"
}
}
}
}{
"servers": {
"s3": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"s3-aws-mcp-server"
],
"env": {
"AWS_ACCESS_KEY_ID": "<AWS_ACCESS_KEY_ID>",
"AWS_SECRET_ACCESS_KEY": "<AWS_SECRET_ACCESS_KEY>"
}
}
}
}Put your own values in place of
<AWS_ACCESS_KEY_ID> (AWS access key ID for authentication), <AWS_SECRET_ACCESS_KEY> (AWS secret access key for authentication).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
AWS_REGION (AWS region for S3 operations), AWS_ENDPOINT_URL (Custom S3 endpoint URL for MinIO or S3-compatible services), S3_FORCE_PATH_STYLE (Use path-style addressing instead of virtual-hosted-style), S3_BUCKET (Constrain all operations to a single bucket), S3_ENABLED_TOOLGROUPS (Comma-separated tool groups: readonly or readwrite), S3_ENABLED_TOOLS (Whitelist specific tools by name), S3_DISABLED_TOOLS (Blacklist specific tools by name), SKIP_HEALTH_CHECKS (Skip AWS credential validation health checks at startup).
Alternatives to S3
same job, measured the same wayMCP server for AWS DynamoDB with fine-grained tool control and configurable access levels.
TypeScript MCP server for AI-powered containerization workflows with Docker and Kubernetes support
SQL Server MCP with RAG capabilities for macOS (Docker SQL Server support)
Rust MCP server and CLI for Arcane Docker and container management.
Enterprise-grade MySQL MCP Server with OAuth 2.0, 106 tools, and Docker deployment
REA reverse-engineering MCP server in Docker, with JADX, Apktool and adb for APKs.
MCP server for Roku device automation — deploy, ECP control, screenshots, and debug console
Cloud replacement for mcp-server-filesystem — 20 tools for S3, Azure Blob, and GCS
S3 — questions
Answers built from our own checks of this server.