OpenWorkspace-o1 AWS S3 MCP Server.
Aws Ow S3 MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Aws Ow S3 MCP directly instead of describing what you should do. OpenWorkspace-o1 AWS S3 MCP Server.
MCP Server for AWS S3 operations, providing secure access to S3 buckets through pre-signed URLs.
Installation goes through your MCP client rather than a global install: point it at Command on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Once Aws Ow S3 MCP is connected, these are the calls the assistant has available:
Input — - prefix (string, optional): Prefix filter for object keysReturns — Array of objects with keys, sizes, and last modified datesInputs — - key (string, required): Object key to retrieveYou will need 6 environment variables: BUCKET_NAME, REGION, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, YOUR_ACCESS_KEY, YOUR_SECRET_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the cloud and infrastructure options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Aws Ow S3 MCP's toolset — Input, Returns, Inputs — is a fair guide to whether it matches your workflow. It is maintained by OpenWorkspace-o1; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Input | - prefix (string, optional): Prefix filter for object keys |
| Returns | Array of objects with keys, sizes, and last modified dates |
| Inputs | - key (string, required): Object key to retrieve |
{
"mcpServers": {
"aws-ow-s3-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"BUCKET_NAME",
"-e",
"REGION",
"-e",
"AWS_ACCESS_KEY_ID",
"-e",
"AWS_SECRET_ACCESS_KEY",
"mcp/aws-ow-s3-mcp"
],
"env": {
"BUCKET_NAME": "<YOUR_BUCKET_NAME>",
"REGION": "<AWS_REGION>",
"AWS_ACCESS_KEY_ID": "<YOUR_ACCESS_KEY>",
"AWS_SECRET_ACCESS_KEY": "<YOUR_SECRET_KEY>"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| BUCKET_NAME | Configuration value read at startup. | Optional |
| REGION | Configuration value read at startup. | Optional |
| AWS_ACCESS_KEY_ID | Credential the server authenticates with. | Yes |
| AWS_SECRET_ACCESS_KEY | Credential the server authenticates with. | Yes |
| YOUR_ACCESS_KEY | Credential the server authenticates with. | Yes |
| YOUR_SECRET_KEY | Credential the server authenticates with. | Yes |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.