GitHub
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Description from the maker (original English)
MCP server for AWS S3 with fine-grained tool control and S3-compatible endpoint support.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_REGION, AWS_ENDPOINT_URL, S3_FORCE_PATH_STYLE, S3_BUCKET, S3_ENABLED_TOOLGROUPS, S3_ENABLED_TOOLS, S3_DISABLED_TOOLS, SKIP_HEALTH_CHECKSValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"s3": {
"command": "npx",
"args": [
"-y",
"s3-aws-mcp-server"
],
"env": {
"AWS_ACCESS_KEY_ID": "your-value",
"AWS_SECRET_ACCESS_KEY": "your-value",
"AWS_REGION": "your-value",
"AWS_ENDPOINT_URL": "your-value",
"S3_FORCE_PATH_STYLE": "your-value",
"S3_BUCKET": "your-value",
"S3_ENABLED_TOOLGROUPS": "your-value",
"S3_ENABLED_TOOLS": "your-value",
"S3_DISABLED_TOOLS": "your-value",
"SKIP_HEALTH_CHECKS": "your-value"
}
}
}
}Run this in your terminal
claude mcp add s3 --env AWS_ACCESS_KEY_ID=your-value --env AWS_SECRET_ACCESS_KEY=your-value --env AWS_REGION=your-value --env AWS_ENDPOINT_URL=your-value --env S3_FORCE_PATH_STYLE=your-value --env S3_BUCKET=your-value --env S3_ENABLED_TOOLGROUPS=your-value --env S3_ENABLED_TOOLS=your-value --env S3_DISABLED_TOOLS=your-value --env SKIP_HEALTH_CHECKS=your-value -- npx -y s3-aws-mcp-serverFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"s3": {
"command": "npx",
"args": [
"-y",
"s3-aws-mcp-server"
],
"env": {
"AWS_ACCESS_KEY_ID": "your-value",
"AWS_SECRET_ACCESS_KEY": "your-value",
"AWS_REGION": "your-value",
"AWS_ENDPOINT_URL": "your-value",
"S3_FORCE_PATH_STYLE": "your-value",
"S3_BUCKET": "your-value",
"S3_ENABLED_TOOLGROUPS": "your-value",
"S3_ENABLED_TOOLS": "your-value",
"S3_DISABLED_TOOLS": "your-value",
"SKIP_HEALTH_CHECKS": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"s3": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"s3-aws-mcp-server"
],
"env": {
"AWS_ACCESS_KEY_ID": "your-value",
"AWS_SECRET_ACCESS_KEY": "your-value",
"AWS_REGION": "your-value",
"AWS_ENDPOINT_URL": "your-value",
"S3_FORCE_PATH_STYLE": "your-value",
"S3_BUCKET": "your-value",
"S3_ENABLED_TOOLGROUPS": "your-value",
"S3_ENABLED_TOOLS": "your-value",
"S3_DISABLED_TOOLS": "your-value",
"SKIP_HEALTH_CHECKS": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
AWS_REGION envAWS_ENDPOINT_URL envS3_FORCE_PATH_STYLE envS3_BUCKET envS3_ENABLED_TOOLGROUPS envS3_ENABLED_TOOLS envS3_DISABLED_TOOLS envSKIP_HEALTH_CHECKS envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain pulsemcp.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.0.5) reached the registry 5 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
MCP server for AWS S3 operations with fine-grained tool access control. Supports read/write operations on S3 buckets and objects, with configurable tool groups for security and permission management.
| Tool | Group | Description |
|---|---|---|
list_buckets | readonly | List all S3 buckets in the AWS account |
list_objects | readonly | List objects in a bucket with prefix and pagination |
get_object | readonly | Get object contents as text |
head_bucket | readonly | Check if a bucket exists and is accessible |
put_object | readwrite | Upload or update an object |
delete_object | readwrite | Delete an object from a bucket |
copy_object | readwrite | Copy an object within or across buckets |
create_bucket | readwrite | Create a new S3 bucket |
delete_bucket | readwrite | Delete an empty S3 bucket |
| Resource | Description |
|---|---|
s3://config | Server configuration and status (for debugging) |
Control which tools are available via the S3_ENABLED_TOOLGROUPS environment variable:
| Group | Description |
|---|---|
readonly | Read-only operations (list, get, head) |
readwrite | Write operations (put, delete, copy, create) |
Examples:
S3_ENABLED_TOOLGROUPS="readonly" - Only read operationsS3_ENABLED_TOOLGROUPS="readonly,readwrite" - All operationsFine-grained control over specific tools:
S3_ENABLED_TOOLS="list_buckets,get_object" - Only enable these toolsS3_DISABLED_TOOLS="delete_bucket,delete_object" - Disable these toolsConstrain all operations to a specific bucket using S3_BUCKET:
S3_BUCKET="my-bucket"
When set:
list_buckets, create_bucket, delete_bucket, head_bucket) are hiddenbucket parameter is automatically injected and hidden from tool inputscopy_object, both source and destination are constrained to the specified bucketThis is useful for restricting access to a single bucket without giving broader S3 permissions.
| Variable | Required | Description | Default |
|---|---|---|---|
AWS_ACCESS_KEY_ID | Yes | AWS access key ID | - |
AWS_SECRET_ACCESS_KEY | Yes | AWS secret access key | - |
AWS_REGION | No | AWS region for S3 operations | us-east-1 |
AWS_ENDPOINT_URL | No | Custom S3 endpoint (for MinIO, etc.) | - |
S3_FORCE_PATH_STYLE | No | Use path-style addressing (for MinIO) | false |
S3_BUCKET | No | Constrain operations to single bucket | - |
S3_ENABLED_TOOLGROUPS | No | Comma-separated tool groups | All enabled |
S3_ENABLED_TOOLS | No | Specific tools to enable | - |
S3_DISABLED_TOOLS | No | Specific tools to disable | - |
SKIP_HEALTH_CHECKS | No | Skip credential validation | false |
If this is your first time using MCP Servers, make sure you have the Claude Desktop application and follow the official MCP setup instructions.
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": { "s3": { "command": "npx", "args": ["-y", "s3-aws-mcp-server"], "env": { "AWS_ACCESS_KEY_ID": "your-access-key-id", "AWS_SECRET_ACCESS_KEY": "your-secret-access-key", "AWS_REGION": "us-east-1", "S3_ENABLED_TOOLGROUPS": "readonly" } } } }
Restart Claude Desktop and you should be ready to go!
For safer exploration, enable only read operations:
{
"env": { "S3_ENABLED_TOOLGROUPS": "readonly" } }
For MinIO, LocalStack, or other S3-compatible services:
{
"env": { "AWS_ACCESS_KEY_ID": "minioadmin", "AWS_SECRET_ACCESS_KEY": "minioadmin", "AWS_REGION": "us-east-1", "AWS_ENDPOINT_URL": "http://localhost:9000", "S3_FORCE_PATH_STYLE": "true" } }
Note: S3_FORCE_PATH_STYLE is required for MinIO and some other S3-compatible services that use path-style addressing (localhost:9000/bucket-name) instead of virtual-hosted-style (bucket-name.localhost:9000).
npm run install-all
npm run build
npm run dev
# Run functional tests
npm run test:run
npm run test:integration
npm run test:manual:setup # First time only npm run test:manual
npm run test:all
Create a .env file in the s3 directory:
AWS_ACCESS_KEY_ID=your_access_key
AWS_SECRET_ACCESS_KEY=your_secret_key AWS_REGION=us-east-1
Then run:
npm run test:manual
s3/
├── local/ # Local server implementation │ ├── src/ │ │ ├── index.ts # Main entry point with env validation │ │ └── index.integration-with-mock.ts │ └── package.json ├── shared/ # Shared business logic │ ├── src/ │ │ ├── server.ts # Server factory with DI │ │ ├── tools.ts # Tool registration with grouping │ │ ├── tools/ # Individual tool implementations │ │ ├── resources.ts # Resource implementations │ │ ├── s3-client/ # AWS S3 client wrapper │ │ └── logging.ts │ └── package.json ├── tests/ # Test suite │ ├── functional/ # Unit tests with mocks │ ├── integration/ # MCP protocol tests │ ├── manual/ # Real API tests │ └── mocks/ # Mock implementations └── package.json # Root workspace config
MIT