# AWS S3 MCP server

> Lets an AI client list, read, upload, copy, and delete S3 buckets and objects with configurable tool access control.

- Repository: https://github.com/pulsemcp/mcp-servers
- Page: https://hostedmcp.org/servers/pulsemcp/s3
- Official: yes
- Transport: stdio
- Stars: 81
- License: MIT
- Latest version: 0.0.5

## Install

### Claude Code

```sh
claude mcp add --env 'AWS_ACCESS_KEY_ID=<YOUR_AWS_ACCESS_KEY_ID>' --env 'AWS_SECRET_ACCESS_KEY=<YOUR_AWS_SECRET_ACCESS_KEY>' s3 -- npx -y s3-aws-mcp-server
```

### Cursor (`~/.cursor/mcp.json`)

```json
{
  "mcpServers": {
    "s3": {
      "command": "npx",
      "args": [
        "-y",
        "s3-aws-mcp-server"
      ],
      "env": {
        "AWS_ACCESS_KEY_ID": "<YOUR_AWS_ACCESS_KEY_ID>",
        "AWS_SECRET_ACCESS_KEY": "<YOUR_AWS_SECRET_ACCESS_KEY>"
      }
    }
  }
}
```

### VS Code (`.vscode/mcp.json`)

```json
{
  "servers": {
    "s3": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "s3-aws-mcp-server"
      ],
      "env": {
        "AWS_ACCESS_KEY_ID": "<YOUR_AWS_ACCESS_KEY_ID>",
        "AWS_SECRET_ACCESS_KEY": "<YOUR_AWS_SECRET_ACCESS_KEY>"
      }
    }
  }
}
```

### VS Code CLI

```sh
code --add-mcp '{"name":"s3","type":"stdio","command":"npx","args":["-y","s3-aws-mcp-server"],"env":{"AWS_ACCESS_KEY_ID":"<YOUR_AWS_ACCESS_KEY_ID>","AWS_SECRET_ACCESS_KEY":"<YOUR_AWS_SECRET_ACCESS_KEY>"}}'
```

### Claude Desktop (`claude_desktop_config.json`)

```json
{
  "mcpServers": {
    "s3": {
      "command": "npx",
      "args": [
        "-y",
        "s3-aws-mcp-server"
      ],
      "env": {
        "AWS_ACCESS_KEY_ID": "<YOUR_AWS_ACCESS_KEY_ID>",
        "AWS_SECRET_ACCESS_KEY": "<YOUR_AWS_SECRET_ACCESS_KEY>"
      }
    }
  }
}
```

### Codex

```sh
codex mcp add s3 --env 'AWS_ACCESS_KEY_ID=<YOUR_AWS_ACCESS_KEY_ID>' --env 'AWS_SECRET_ACCESS_KEY=<YOUR_AWS_SECRET_ACCESS_KEY>' -- npx -y s3-aws-mcp-server
```

### Codex config.toml (`~/.codex/config.toml`)

```toml
[mcp_servers.s3]
command = "npx"
args = ["-y", "s3-aws-mcp-server"]

[mcp_servers.s3.env]
AWS_ACCESS_KEY_ID = "<YOUR_AWS_ACCESS_KEY_ID>"
AWS_SECRET_ACCESS_KEY = "<YOUR_AWS_SECRET_ACCESS_KEY>"
```

### Gemini CLI

```sh
gemini mcp add -s user -e 'AWS_ACCESS_KEY_ID=<YOUR_AWS_ACCESS_KEY_ID>' -e 'AWS_SECRET_ACCESS_KEY=<YOUR_AWS_SECRET_ACCESS_KEY>' s3 npx -- -y s3-aws-mcp-server
```

### Gemini settings.json (`~/.gemini/settings.json`)

```json
{
  "mcpServers": {
    "s3": {
      "command": "npx",
      "args": [
        "-y",
        "s3-aws-mcp-server"
      ],
      "env": {
        "AWS_ACCESS_KEY_ID": "<YOUR_AWS_ACCESS_KEY_ID>",
        "AWS_SECRET_ACCESS_KEY": "<YOUR_AWS_SECRET_ACCESS_KEY>"
      }
    }
  }
}
```

## Environment variables

| Name | Required | Secret | Description |
|---|---|---|---|
| `AWS_ACCESS_KEY_ID` | yes | yes | AWS access key ID for authentication. |
| `AWS_SECRET_ACCESS_KEY` | yes | yes | AWS secret access key for authentication. |
| `AWS_ENDPOINT_URL` | no | no | Custom S3 endpoint URL for MinIO or S3-compatible services. |
| `AWS_REGION` | no | no | AWS region for S3 operations. |
| `S3_BUCKET` | no | no | Constrain all operations to a single bucket. |
| `S3_DISABLED_TOOLS` | no | no | Blacklist specific tools by name. |
| `S3_ENABLED_TOOLGROUPS` | no | no | Comma-separated tool groups: readonly or readwrite. |
| `S3_ENABLED_TOOLS` | no | no | Whitelist specific tools by name. |
| `S3_FORCE_PATH_STYLE` | no | no | Use path-style addressing instead of virtual-hosted-style. |
| `SKIP_HEALTH_CHECKS` | no | no | Skip AWS credential validation health checks at startup. |

## Tools (11)

- `list_buckets`
- `list_objects`
- `get_object`
- `head_bucket`
- `put_object`
- `delete_object`
- `copy_object`
- `create_bucket`
- `delete_bucket`
- `readonly`
- `readwrite`

## FAQ

### Can I restrict the S3 MCP server to read-only operations?

Yes. Set the S3_ENABLED_TOOLGROUPS environment variable to "readonly" to expose only list, get, and head tools.

### Does the S3 MCP server work with MinIO or LocalStack?

Yes, it supports S3-compatible endpoints via AWS_ENDPOINT_URL, and you should also set S3_FORCE_PATH_STYLE to true for path-style addressing.

### How do I limit the server to a single bucket?

Set the S3_BUCKET environment variable; all object operations are scoped to that bucket and bucket-level tools are hidden.

### Which credentials does the server need?

It requires AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY, with AWS_REGION defaulting to us-east-1.

### Can I disable specific tools individually?

Yes, use S3_DISABLED_TOOLS to turn off named tools or S3_ENABLED_TOOLS to allow only listed ones.
