io.github.kinginsun/mcp-aliyun-oss
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@io.github.kinginsun/mcp-aliyun-oss Upload /tmp/report.pdf to OSS with prefix agents/reports"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-aliyun-oss
Standalone MCP server (Python SDK 2.x MCPServer) with one tool, oss-upload: put an object on Aliyun OSS named {prefix}/{md5}{ext}.
Repository: github.com/kinginsun/mcp-aliyun-oss
Credentials are read from the environment only. Never put AccessKeys in this repo or in chat.
Tool: oss-upload
Provide exactly one source:
Argument | Use when | Bytes | Extension |
| File already on disk | Read the absolute path | Path suffix; optional |
| Generated text (HTML / Markdown / JSON) | UTF-8 | Required |
| Binary |
| Same as |
Other arguments:
oss_path_prefix— defaultagents/docs. Must start withagents/. No...Return value:
{ status, file_size, key, url }(file_sizeis decoded bytes).
Decoded size cap is 100MB. Large files: pass local_file_path. Do not send huge base64 over stdio.
Related MCP server: Tencent Cloud COS MCP Server
Environment
Required (or the OSS_TEST_* aliases):
Variable | Meaning |
| AccessKey ID |
| AccessKey Secret |
| Bucket name |
| Regional endpoint without |
Optional: OSS_PUBLIC_URL_BASE (CDN / custom domain), OSS_CONNECT_TIMEOUT (seconds, default 120).
If OSS_PUBLIC_URL_BASE is set, url is {base}/{key}; otherwise https://{bucket}.{endpoint}/{key}.
Copy .env.example to a local .env for development; do not commit .env.
Install
From PyPI (after release):
uv tool install mcp-aliyun-oss
# or: pip install mcp-aliyun-ossFrom source:
git clone https://github.com/kinginsun/mcp-aliyun-oss.git
cd mcp-aliyun-oss
uv sync --extra devCursor (~/.cursor/mcp.json)
PyPI / uvx (recommended for end users):
{
"mcpServers": {
"aliyun-oss": {
"command": "uvx",
"args": ["mcp-aliyun-oss"],
"env": {
"OSS_ACCESS_KEY_ID": "your-id",
"OSS_ACCESS_KEY_SECRET": "your-secret",
"OSS_BUCKET": "your-bucket",
"OSS_ENDPOINT": "oss-cn-hangzhou.aliyuncs.com"
}
}
}
}Local checkout (development):
{
"mcpServers": {
"aliyun-oss": {
"command": "uv",
"args": ["run", "--directory", "/path/to/mcp-aliyun-oss", "mcp-aliyun-oss"],
"env": {
"OSS_ACCESS_KEY_ID": "your-id",
"OSS_ACCESS_KEY_SECRET": "your-secret",
"OSS_BUCKET": "your-bucket",
"OSS_ENDPOINT": "oss-cn-hangzhou.aliyuncs.com"
}
}
}
}Tests
uv run pytestOSS put_object is mocked; no live bucket is required.
Publish (maintainers)
GitHub — push to
https://github.com/kinginsun/mcp-aliyun-oss(public).PyPI — bump
versioninpyproject.tomlandserver.json, then either:GitHub Release with tag
v0.1.0(workflow.github/workflows/publish-pypi.ymluses secretPYPI_API_TOKEN), orLocal:
uv build && uv publishwith a PyPI API token.
MCP Registry — after the same version is on PyPI, install mcp-publisher, log in with GitHub, and from this repo run
mcp-publisher publish(uses rootserver.json).
Registry server name: io.github.kinginsun/mcp-aliyun-oss.
License
MIT
Available Tools
1 tooloss-uploadA
Upload a file to Aliyun OSS. Object name is MD5(content) + extension under an agents/ prefix.
Provide exactly one source:
local_file_path: absolute path on the machine running this MCP server
content: UTF-8 text (generated HTML/Markdown/JSON); requires filename
content_base64: binary (optional data:*;base64, prefix); requires filename
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}.
Inputs: content, filename, content_base64, local_file_path, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Cloud file relay: chunked uploads, folders, share links, inline text reads, ZIP packing.
Hosted file storage for agents: upload, list, download, share by link, expire, scratch.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables large language models to upload files directly to Alibaba Cloud Object Storage Service (OSS), supporting multiple OSS configurations and specified upload directories.15 npm7MIT
- AlicenseBqualityDmaintenanceEnables interaction with Tencent Cloud Object Storage (COS) through MCP protocol. Supports file upload, download, deletion, listing objects, and generating temporary signed URLs for cloud storage management.535 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables uploading files to MinIO (S3 compatible) via MCP tools. Supports Base64 file upload and optional curl command generation.-
- AlicenseNot gradedqualityDmaintenance将图片URL转存到阿里云OSS并返回CDN访问地址,支持OSS直传和HOOK代理两种模式。20 npmMIT