com.pulsemcp/s3

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

com.pulsemcp/s3 · Repository · version 0.0.5 · 77 stars · listed from registry

Install

The sweep installs into a clean prefix, but this is the command a user would run:

npx s3-aws-mcp-server

Needs credentials: AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY. The probe used placeholder values, so an amber needs credentials result below means the server asked for the real ones, not that it is broken. Maintainers: how to go green.

Results by platform

Linux

needs credentials2026-08-16 · probed over npm

2 recorded runs, oldest first.

handshake failed: MCP error -32000: Connection closed
--- stderr (tail) ---
[ERROR] healthcheck: Failed to validate AWS credentials: The AWS Access Key Id you provided does not exist in our records.
[ERROR] healthcheck: Please check your AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY

macOS

needs credentials2026-08-16 · probed over npm

2 recorded runs, oldest first.

handshake failed: MCP error -32000: Connection closed
--- stderr (tail) ---
[ERROR] healthcheck: Failed to validate AWS credentials: The AWS Access Key Id you provided does not exist in our records.
[ERROR] healthcheck: Please check your AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY

Windows

needs credentials2026-08-15 · probed over npm

1 recorded run, oldest first.

handshake failed: MCP error -32000: Connection closed
--- stderr (tail) ---
[ERROR] healthcheck: Failed to validate AWS credentials: The AWS Access Key Id you provided does not exist in our records.
[ERROR] healthcheck: Please check your AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY

Badge

Paste this into the project README to show the current result:

[![does it install](https://img.shields.io/endpoint?url=https://doesitinstall.com/badge/com.pulsemcp__s3.json)](https://doesitinstall.com/s/com.pulsemcp__s3.html)