aws-s3-connector-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APP_HOST | No | Bind host for SSE or Streamable HTTP | 0.0.0.0 |
| APP_PORT | No | Bind port for SSE or Streamable HTTP | 8000 |
| AWS_REGION | No | AWS region (default: auto-detected or us-east-1) | |
| TRANSPORT_TYPE | No | Transport type: stdio, sse, or streamable-http | stdio |
| AWS_ACCESS_KEY_ID | No | AWS access key for private buckets | |
| AWS_SECRET_ACCESS_KEY | No | AWS secret key for private buckets |
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 | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| connect_s3A | Connect to an AWS S3 bucket. Supports two modes:
|
| list_objectsA | List all objects in the connected S3 bucket. Returns each object's file name, size, last modified date, and a presigned URL. Optionally filter by prefix (folder path) or limit the number of results. |
| upload_objectA | Upload a file to the connected S3 bucket. Two sources supported:
|
| read_objectA | Read and display the contents of an object in the connected S3 bucket. Supported formats:
|
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 4 tools
Each tool has a distinct purpose: connect to a bucket, list objects, read object contents, and upload files. There is no overlap in functionality.
All tool names follow a consistent verb_noun pattern with snake_case (connect_s3, list_objects, read_object, upload_object), making them predictable.
With 4 tools covering core S3 operations (connect, list, read, upload), the count is well-scoped and avoids being too few or too many.
The tool surface covers key read and write operations, but is missing a delete operation, which is a minor gap. Overall, it supports common workflows.