io.github.kinginsun/mcp-aliyun-oss
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OSS_BUCKET | No | Bucket name. | |
| OSS_ENDPOINT | No | Regional endpoint without https://, e.g. oss-cn-shenzhen.aliyuncs.com. | |
| OSS_TEST_BUCKET | No | Alternative bucket name using the OSS_TEST_* alias. | |
| OSS_ACCESS_KEY_ID | No | Aliyun OSS AccessKey ID. | |
| OSS_TEST_ENDPOINT | No | Alternative endpoint using the OSS_TEST_* alias. | |
| OSS_CONNECT_TIMEOUT | No | Connection timeout in seconds. | 120 |
| OSS_PUBLIC_URL_BASE | No | Optional CDN or custom domain base URL. | |
| OSS_ACCESS_KEY_SECRET | No | Aliyun OSS AccessKey Secret. | |
| OSS_TEST_ACCESS_KEY_ID | No | Alternative AccessKey ID using the OSS_TEST_* alias. | |
| OSS_TEST_ACCESS_KEY_SECRET | No | Alternative AccessKey Secret using the OSS_TEST_* alias. |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| oss-uploadA | Upload a file to Aliyun OSS. Object name is MD5(content) + extension under an agents/ prefix. Provide exactly one source:
filename is required for content / content_base64 and may override the suffix when using a path. Example: report.html. Prefix default agents/docs; must start with agents/. Decoded size cap 100MB — large files use local_file_path. Credentials: OSS_ACCESS_KEY_ID, OSS_ACCESS_KEY_SECRET, OSS_BUCKET, OSS_ENDPOINT (or OSS_TEST_*). Returns {status, file_size, key, url}. |
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
Only one tool exists, so there is no risk of an agent confusing it with another tool. The single oss-upload tool has a clear, singular purpose.
The tool name oss-upload follows a clear verb_noun style and is internally consistent. However, with only one tool there is no broader set of names to compare against for a full consistency assessment.
A single upload tool is far too narrow for a server named mcp-aliyun-oss, which implies broader object storage capabilities. Even if the intent is upload-only, one tool feels under-scoped for the apparent domain.
The server only supports uploading files and lacks common OSS operations such as listing, retrieving, deleting, or generating presigned URLs. This is a significant functional gap that would force agents to rely on external tooling for basic object lifecycle management.