io.github.nagarjunr/data-connectors-s3 (MCP)

This is a read-only Model Context Protocol (MCP) server that provides access to S3-compatible storage. It supports listing buckets and objects, enabling developers to browse available data in an object-storage environment without write operations.

🛠️ Key Features

Read-only access to S3-compatible storage
List buckets
List objects

🚀 Use Cases

Data exploration for object-storage sources
Integrating S3-compatible resources into AI agent and RAG workflows
Building data pipelines that require inventorying existing buckets and objects

⚡ Developer Benefits

Simple connector surface focused on bucket and object listing
Compatible with developer use cases tagged for AI agents, data connectors, and data pipelines
Aligns with S3-focused ecosystems (topics include s3 and data-connectors)

⚠️ Limitations

Read-only operations (no upload or modification implied)
Limited to listing buckets and objects based on provided description

Topics

ai-agents, connector, data-connectors, data-pipeline, google-cloud-storage, llm, onedrive, postgresql, python, rag, s3, sharepoint

S3 MCP Server

Read-only MCP server exposing S3Client to AI agents: list buckets and objects on any S3-compatible endpoint.

Tools

Tool	Description
`list_buckets() -> list[str]`	List all accessible buckets
`list_objects(bucket: str, prefix: str = "") -> list[str]`	List object keys in a bucket, optionally filtered by prefix
`read_object_text(bucket: str, key: str, max_bytes: int = 1_000_000) -> str`	Read an object's content as UTF-8 text. Refuses (raises) objects larger than `max_bytes` rather than truncating.
`get_presigned_url(bucket: str, key: str, expires_in: int = 300) -> str`	Time-limited, read-only GET URL — for content beyond `read_object_text`'s inline cap

download_file() writes to a local filesystem path an agent doesn't have (use read_object_text for small text content instead); upload_file(), upload_file_multipart(), delete_object(), and cleanup_prefix() are write/destructive and are not exposed as tools.

Tested against a real MinIO container, not mocks.

Environment Variables

Variable	Required	Default	Notes
`S3_ENDPOINT`	yes	—	S3-compatible endpoint URL
`AWS_ACCESS_KEY_ID`	yes	—	Read-only credentials recommended
`AWS_SECRET_ACCESS_KEY`	yes	—
`S3_REGION`	no	`us-east-1`

Run locally

bash

pip install "data-connectors-ai[s3,mcp]"
data-connectors-s3-mcp

Use with an MCP client

json

{
  "mcpServers": {
    "s3": {
      "command": "uvx",
      "args": ["--from", "data-connectors-ai[s3,mcp]", "data-connectors-s3-mcp"],
      "env": {
        "S3_ENDPOINT": "https://s3.your-provider.com",
        "AWS_ACCESS_KEY_ID": "...",
        "AWS_SECRET_ACCESS_KEY": "..."
      }
    }
  }
}

Registry

Published at io.github.nagarjunr/data-connectors-s3 on the official MCP registry.

S3 Connector

io.github.nagarjunr/data-connectors-s3 (MCP)

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

Topics

S3 MCP Server

Tools

Environment Variables

Run locally

Use with an MCP client

Registry

Install

Configuration