S3 MCP server
{
"mcpServers": {
"pulsemcp-s3": {
"command": "npx",
"args": [
"-y",
"s3-aws-mcp-server@latest"
],
"env": {
"AGENT_ORCHESTRATOR_BASE_URL": "https://...",
"FLY_IO_API_TOKEN": "<fly_io_api_token>"
}
}
}
}{
"mcpServers": {
"pulsemcp-s3": {
"command": "npx",
"args": [
"-y",
"s3-aws-mcp-server@latest"
],
"env": {
"AGENT_ORCHESTRATOR_BASE_URL": "https://...",
"FLY_IO_API_TOKEN": "<fly_io_api_token>"
}
}
}
}{
"mcpServers": {
"pulsemcp-s3": {
"command": "npx",
"args": [
"-y",
"s3-aws-mcp-server@latest"
],
"env": {
"AGENT_ORCHESTRATOR_BASE_URL": "https://...",
"FLY_IO_API_TOKEN": "<fly_io_api_token>"
}
}
}
}{
"servers": {
"pulsemcp-s3": {
"command": "npx",
"args": [
"-y",
"s3-aws-mcp-server@latest"
],
"env": {
"AGENT_ORCHESTRATOR_BASE_URL": "${input:agent_orchestrator_base_url}",
"FLY_IO_API_TOKEN": "${input:fly_io_api_token}"
}
}
},
"inputs": [
{
"id": "agent_orchestrator_base_url",
"type": "promptString",
"description": "Agent orchestrator base url",
"password": true
},
{
"id": "fly_io_api_token",
"type": "promptString",
"description": "Fly io api token",
"password": true
}
]
}{
"mcpServers": {
"pulsemcp-s3": {
"command": "npx",
"args": [
"-y",
"s3-aws-mcp-server@latest"
],
"env": {
"AGENT_ORCHESTRATOR_BASE_URL": "https://...",
"FLY_IO_API_TOKEN": "<fly_io_api_token>"
}
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsoninstall npx -y s3-aws-mcp-serverversion 0.0.5
What it does
This MCP server provides access to AWS S3 with fine-grained tool control and support for S3-compatible endpoints. It is designed for developers and AI agents that need to interact with S3 buckets and objects programmatically.
- Upload, download, or delete files in S3 buckets as part of an agentic workflow.
- List and inspect the contents of S3 buckets to retrieve object metadata and organize files.
- Work with S3-compatible storage services that follow the S3 API specification.
This entry comes from the registry but points to no public repository, so there is nothing to check: no commit history, no source, no tool list. It is listed for completeness and left out of search engines.
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.