S3 Uploader MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AWS_REGION | Yes | Your AWS region | |
| BUCKET_NAME | Yes | The name of your S3 bucket | |
| 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 |
|---|---|
| upload_fileA | Upload a file to S3 bucket. The file will be uploaded with automatic MIME type detection based on file extension. Requires AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_REGION, and BUCKET_NAME environment variables to be set. |
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 1 tool
With only one tool, there is no possibility of confusion. The upload_file tool clearly defines its purpose and input.
The single tool name 'upload_file' follows a clear verb_noun pattern, consistent with common conventions.
The server provides only one tool, which is borderline thin but appropriate for a narrowly-scoped uploader service.
For an S3 uploader, the upload_file tool covers the essential operation thoroughly, with no obvious missing functionality within the stated scope.