mcp-s3-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AWS_ACCESS_KEY_ID | No | AWS access key ID for authentication | |
| AWS_DEFAULT_REGION | No | AWS region (e.g., us-east-1) | |
| AWS_SECRET_ACCESS_KEY | No | AWS secret access key for authentication |
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 |
|---|---|
| test_connectionC | Test MCP S3 server connection |
| list_s3_bucketsA | List all S3 buckets in your storage account (supports AWS S3, DigitalOcean Spaces, IBM Cloud Object Storage, and other S3-compatible services) |
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 2 tools
The two tools have clearly distinct purposes: listing buckets vs. testing connection. No overlap exists.
Both tools use a consistent verb_noun pattern in snake_case (list_s3_buckets, test_connection).
With only 2 tools for an S3 server, the set feels too thin. Typical S3 services require many more operations (e.g., object CRUD, bucket management).
The server lacks essential S3 operations such as listing objects, uploading/downloading files, and creating/deleting buckets, making the tool surface severely incomplete.