AWS S3 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Set log level (e.g., info, debug) | info |
| AWS_REGION | Yes | AWS region (e.g., us-east-1) | |
| ALLOW_WRITE | No | Enable write operations (presigned PUT URLs) | false |
| AWS_ACCESS_KEY_ID | Yes | Your AWS access key ID | |
| AWS_SECRET_ACCESS_KEY | Yes | Your AWS secret access key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| s3_list_bucketsA | List all S3 buckets in the AWS account |
| s3_list_objectsA | List objects in an S3 bucket with optional prefix filtering |
| s3_presign_getA | Generate a presigned URL for downloading an object from S3 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct S3 resource and action: listing buckets, listing objects, and generating a presigned GET URL. No overlap or ambiguity between them.
All tools follow a consistent s3_verb_noun pattern, using clear, lowercase snake_case. The naming uniformly indicates the service and the operation.
Three tools is a compact set, slightly on the low side, but reasonable for a focused S3 access server. Each tool serves a distinct, useful function without redundancy.
The server only supports listing and presigned downloads, lacking any write or delete operations. For a general S3 server, this is notably incomplete; it appears read-only, which may be acceptable for a narrow use case but leaves significant functional gaps.