
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.
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.
Installation
In SourceWeft
- Open S3 in the dashboard and add it to a workspace.
- 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
Resources
Tool Groups
Control which tools are available via the S3_ENABLED_TOOLGROUPS environment variable:
Examples:
S3_ENABLED_TOOLGROUPS="readonly"- Only read operationsS3_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 toolsS3_DISABLED_TOOLS="delete_bucket,delete_object"- Disable these tools
Single Bucket Mode
Constrain all operations to a specific bucket using S3_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
bucketparameter 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
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
Restart Claude Desktop and you should be ready to go!
Read-Only Mode
For safer exploration, enable only read operations:
Using with S3-Compatible Services
For MinIO, LocalStack, or other S3-compatible services:
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
Build
Running in Development Mode
Testing
Manual Testing Setup
Create a .env file in the s3 directory:
Then run:
Project Structure
License
MIT
Source: experimental/s3/README.md at commit 0ed34de
Tools
0Version history
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