S3

com.pulsemcpPublished by pulsemcp.comv0.0.5Updated Oct 24, 2026

MCP server for AWS S3 with fine-grained tool control and S3-compatible endpoint support.

VerifiedSTDIODesktop onlyCloud & InfrastructureFiles & Storage

Overview

AI-generated overview

Local MCP server that lets an assistant list, read, upload, copy and delete AWS S3 buckets and objects, with tool groups to limit it to read-only.

What you can do
List and inspect buckets and objects, including prefix and pagination listing, object contents as text, and bucket existence checks. Upload or update objects, copy objects within or across buckets, and delete objects. Create and delete buckets. Restrict the available tools by group (readonly or readwrite) or by individual tool names, and optionally scope everything to one bucket. Expose a configuration resource for debugging.
When to use it
Useful when an assistant should work directly with files stored in S3 or an S3-compatible service such as MinIO or LocalStack, for example to browse stored objects, read their contents, or manage uploads and cleanup. Read-only mode suits exploration; write mode suits deliberate bucket and object maintenance.
Requirements
Runs locally via npx (Node.js). Requires AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY; AWS_REGION defaults to us-east-1. Optional AWS_ENDPOINT_URL and S3_FORCE_PATH_STYLE for S3-compatible services, S3_BUCKET to constrain to one bucket, and the tool-group and tool-list variables to limit access. Network access to AWS or the custom endpoint.
Before you install
The credentials are real AWS keys, so grant only the S3 permissions needed. Write tools can upload, overwrite, copy and delete objects and create or delete buckets; by default all tools are enabled, so set the readonly group or disable delete tools when that is not intended. A single-bucket setting narrows scope but does not change the key's own permissions.

Installation

In SourceWeft

  1. Open S3 in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

S3 MCP Server

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.

Highlights

  • Full S3 bucket and object management (list, get, put, copy, delete)
  • Fine-grained access control with tool groups (readonly, readwrite)
  • Individual tool enable/disable via environment variables
  • AWS credential validation with health checks
  • S3-compatible endpoint support (MinIO, LocalStack, etc.)
  • TypeScript with strict type checking
  • Comprehensive testing (functional, integration, manual)

Capabilities

Tools

ToolGroupDescription
list_bucketsreadonlyList all S3 buckets in the AWS account
list_objectsreadonlyList objects in a bucket with prefix and pagination
get_objectreadonlyGet object contents as text
head_bucketreadonlyCheck if a bucket exists and is accessible
put_objectreadwriteUpload or update an object
delete_objectreadwriteDelete an object from a bucket
copy_objectreadwriteCopy an object within or across buckets
create_bucketreadwriteCreate a new S3 bucket
delete_bucketreadwriteDelete an empty S3 bucket

Resources

ResourceDescription
s3://configServer configuration and status (for debugging)

Tool Groups

Control which tools are available via the S3_ENABLED_TOOLGROUPS environment variable:

GroupDescription
readonlyRead-only operations (list, get, head)
readwriteWrite operations (put, delete, copy, create)

Examples:

  • S3_ENABLED_TOOLGROUPS="readonly" - Only read operations
  • S3_ENABLED_TOOLGROUPS="readonly,readwrite" - All operations
  • Not set - All tools enabled (default)

Individual Tool Control

Fine-grained control over specific tools:

  • S3_ENABLED_TOOLS="list_buckets,get_object" - Only enable these tools
  • S3_DISABLED_TOOLS="delete_bucket,delete_object" - Disable these tools

Single Bucket Mode

Constrain all operations to a specific bucket using S3_BUCKET:

bash
S3_BUCKET="my-bucket"

When set:

  • All object operations are automatically scoped to this bucket
  • Bucket-level tools (list_buckets, create_bucket, delete_bucket, head_bucket) are hidden
  • The bucket parameter is automatically injected and hidden from tool inputs
  • For copy_object, both source and destination are constrained to the specified bucket

This is useful for restricting access to a single bucket without giving broader S3 permissions.

Quick Start

Configuration

Environment Variables
VariableRequiredDescriptionDefault
AWS_ACCESS_KEY_IDYesAWS access key ID-
AWS_SECRET_ACCESS_KEYYesAWS secret access key-
AWS_REGIONNoAWS region for S3 operationsus-east-1
AWS_ENDPOINT_URLNoCustom S3 endpoint (for MinIO, etc.)-
S3_FORCE_PATH_STYLENoUse path-style addressing (for MinIO)false
S3_BUCKETNoConstrain operations to single bucket-
S3_ENABLED_TOOLGROUPSNoComma-separated tool groupsAll enabled
S3_ENABLED_TOOLSNoSpecific tools to enable-
S3_DISABLED_TOOLSNoSpecific tools to disable-
SKIP_HEALTH_CHECKSNoSkip credential validationfalse

Claude Desktop Configuration

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

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!

Read-Only Mode

For safer exploration, enable only read operations:

json
{  "env": {    "S3_ENABLED_TOOLGROUPS": "readonly"  }}

Using with S3-Compatible Services

For MinIO, LocalStack, or other S3-compatible services:

json
{  "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).

Development

Install Dependencies

bash
npm run install-all

Build

bash
npm run build

Running in Development Mode

bash
npm run dev

Testing

bash
# Run functional testsnpm run test:run
# Run integration tests (full MCP protocol)npm run test:integration
# Run manual tests (real AWS - requires .env)npm run test:manual:setup  # First time onlynpm run test:manual
# Run all automated testsnpm run test:all

Manual Testing Setup

Create a .env file in the s3 directory:

bash
AWS_ACCESS_KEY_ID=your_access_keyAWS_SECRET_ACCESS_KEY=your_secret_keyAWS_REGION=us-east-1

Then run:

bash
npm run test:manual

Project Structure

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

License

MIT

Source: experimental/s3/README.md at commit 0ed34de

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.0.5LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts