
S3
Connects to AWS S3 or any S3-compatible storage endpoint (like MinIO or Backblaze B2) to manage buckets and objects through MCP. You get fine-grained control over which S3 operations are exposed as tools, so you can limit an agent to read-only access or specific bucket operations without opening up your entire S3 account. Built by PulseMCP as an experimental server, meaning they'll maintain it unless AWS ships something better. Requires AWS credentials and supports the standard S3 operations you'd expect: creating buckets, uploading and downloading objects, listing contents, managing permissions. Reach for this when you need an AI agent to interact with S3 storage as part of a larger workflow.
- auth
- Secret needed
- transport
- STDIO
- env vars
- 10
- last updated
- Jun 14, 2026
Sponsors
Configuration
AWS_ACCESS_KEY_ID*secretAWS access key ID for authentication.
AWS_SECRET_ACCESS_KEY*secretAWS secret access key for authentication.
AWS_REGIONdefault: us-east-1AWS region for S3 operations.
AWS_ENDPOINT_URLCustom S3 endpoint URL for MinIO or S3-compatible services.
S3_FORCE_PATH_STYLEdefault: falseUse path-style addressing instead of virtual-hosted-style.
S3_BUCKETConstrain all operations to a single bucket.
S3_ENABLED_TOOLGROUPSComma-separated tool groups: readonly or readwrite.
S3_ENABLED_TOOLSWhitelist specific tools by name.
S3_DISABLED_TOOLSBlacklist specific tools by name.
SKIP_HEALTH_CHECKSdefault: falseSkip AWS credential validation health checks at startup.
Readme
PulseMCP's MCP Servers
We build reliable servers thoughtfully designed for MCP Client-powered workflows.
Design principles
You can have confidence that any Pulse-branded MCP server was built with these north stars in mind:
Details
- Repository
- github.com/pulsemcp/mcp-servers
- Category
- Cloud & Infrastructure
- Package
s3-aws-mcp-server- Transport
- STDIO
- Auth
- Required
- Registry
- MCP registry, active