list_bucketsLABSCO SUMMARY
S3 as tools, for the agent pipelines that end there.
Fetching documents for retrieval, persisting outputs, moving files mid-task — all of it lands in S3, and each one otherwise needs custom glue. The whole surface is here including the policy calls, and the listing tools can be put on autoApprove so read-only use runs without prompts.
What it is
An MCP server over the AWS S3 API. Buckets are listed, created and deleted; objects are listed with a prefix filter, uploaded from a file or a string, downloaded and deleted; bucket policies are read and set. It uses whatever AWS credentials the environment already provides.
What you get
- Every bucket in the account listed
- A bucket created, and an empty bucket deleted
- Objects in a bucket listed, with an optional prefix filter
- A file or a string uploaded as an object
- An object downloaded, and an object deleted
- A bucket policy read and set
Requirements
Node.js 18+ and an AWS account with S3 access. Credentials come from AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY alongside AWS_REGION, from an IAM role, or from an existing aws configure profile with only AWS_REGION set. The client runs it with npx @gangadharrr/aws-s3.
Setup effort
One command — npx @gangadharrr/aws-s3
USE CASES
Getting a document out of a bucket
Filter by prefix to find it, then download the object rather than pasting its contents by hand.
Persisting what the agent produced
Upload a file or a string straight to the bucket, so the output survives the session.
Setting up storage for a new job
Create the bucket and set its policy in the same exchange, before anything is written into it.
Auditing who can read a bucket
Walk the account's buckets and read each policy, without opening the console.
Cleaning up after a run
Remove the objects, then the empty bucket, so a temporary workspace does not linger on the bill.
9 tools
Listed in project docs. Your client may show a different list.
create_bucketdelete_bucketlist_objectsupload_objectdownload_objectdelete_objectget_bucket_policyset_bucket_policyBEFORE YOU INSTALL
What to know first
Tools you get
9 tools named in the project's documentation.
Requires
- npx on PATH
- Node.js 18+
Optional
- AWS_ACCESS_KEY_ID in your environment
- AWS_SECRET_ACCESS_KEY in your environment
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
npx @gangadharrr/aws-s3MCP Clients
Claude Desktop, Cursor
{
"mcpServers": {
"aws-s3": {
"command": "npx",
"args": [
"@gangadharrr/aws-s3"
],
"env": {
"AWS_REGION": "us-east-1",
"AWS_ACCESS_KEY_ID": "<YOUR_AWS_ACCESS_KEY_ID>",
"AWS_SECRET_ACCESS_KEY": "<YOUR_AWS_SECRET_ACCESS_KEY>"
},
"autoApprove": [
"list_buckets",
"list_objects",
"get_bucket_policy"
]
}
}
}