Connect your AI Agents to Amazon S3 in minutes

What is an Amazon S3 MCP?

It's an MCP server that gives your agents access to Amazon S3 storage via tools. Your agents can invoke these tools to list objects in a bucket, read file contents, upload new files, generate presigned download links, and more.

AWS offers an official MCP server, but you can also use one from a third-party platform, like Merge Agent Handler.

How can I use the Amazon S3 MCP server?

The use cases naturally depend on the agent you've built, but here are a few common ones:

• Automated report archiving: When a data pipeline finishes a processing run, an agent uploads the output files to a designated S3 bucket with a structured prefix and timestamp, making them available for downstream analytics tools without manual file transfers

• Document processing pipeline: When a new file lands in an S3 intake prefix, an agent reads the object content, routes it to a document processing or extraction service, and writes the structured output back to a processed/ prefix in the same bucket

• Secure asset delivery: When a customer requests access to a report or export file stored in S3, an agent generates a presigned URL scoped to that object and sends it via email or embeds it in a CRM record, avoiding the need to make the bucket public

• Storage cost management: An agent scans a logs/ prefix for objects older than a defined retention window, flags them in a spreadsheet for review, and deletes confirmed stale files to reduce storage spend

What are popular tools for Amazon S3's MCP server?

Here are some of the most commonly used tools:

• list_objects: returns objects in a specified bucket and prefix, with optional filters for key pattern or last-modified date. Useful for agents that need to discover what files exist before reading or processing them

• get_object: downloads the content of a specific S3 object and returns it to the agent. Call this when an agent needs to read a file's contents to parse, summarize, or route it downstream

• put_object: uploads a file or text payload to a specified S3 key. Good for workflows where an agent produces output that needs to be persisted to cloud storage for other systems to consume

• delete_object: removes a specific object from a bucket. Use this when an agent is running a cleanup or archival workflow and needs to free up storage after files have been processed or expired

• create_presigned_url: generates a time-limited URL that grants temporary access to a private S3 object without changing bucket permissions. Helpful when an agent needs to share a file securely with an external user or downstream service

• copy_object: copies an object from one S3 location to another within or across buckets. Use this when an agent needs to move processed files into an archive prefix or replicate objects between environments

What makes Merge Agent Handler's Amazon S3 MCP server better than alternative Amazon S3 MCP servers?

Using Merge Agent Handler for your Amazon S3 MCP server gives you capabilities that community implementations or self-built integrations typically don't include:

• Enterprise-grade security and DLP: Merge Agent Handler includes built-in data loss prevention controls that let you block or redact sensitive fields before they reach an agent. For Amazon S3, this means you can prevent file contents, object metadata, and access patterns tied to sensitive data in your buckets from being exposed even when the agent has broad read access

• Managed authentication and credentials: Merge stores and manages your AWS credentials on your behalf. You never embed access keys or IAM secrets in agent configuration, and you don't need to rotate them manually when they change

• Real-time observability and audit trail: Every tool call against Amazon S3 is captured with full context: bucket name, object key, operation type, and response status. You get a searchable audit log of every file an agent read, wrote, or deleted without writing any logging code

• Tool Packs and controlled access: Tool Packs let you bundle specific Amazon S3 tools with tools from other connectors into a single MCP endpoint, scoped to a specific use case. An agent gets exactly the tools it needs, nothing more

How can I start using Merge Agent Handler's Amazon S3 MCP server?

You can take the following steps:

1. Create or log into your Merge Agent Handler account and navigate to Tool Packs (collections of connector tools scoped to a specific use case).

2. Create a new Tool Pack, then find and enable the Amazon S3 connector. Select the tools that fit your use case: read-only tools like list_objects and get_object are enough for processing workflows, while put_object and delete_object are needed if your agent needs to write or clean up files.

3. Add a Registered User inside the Tool Pack. This is the identity context under which your agent operates. Merge generates a unique MCP URL scoped to this user once it's created.

4. From the Registered User detail page, connect Amazon S3 by entering your AWS credentials. Merge stores and manages those credentials going forward.

5. Copy the MCP URL from the Tool Pack detail page and generate an API key from Settings. You'll need both to connect your agent.

6. Add the MCP server to your agent or IDE using the MCP URL and API key. Your Amazon S3 tools are now accessible through that endpoint.