list_oss_configs
Lists the available Alibaba Cloud OSS configurations.
LABSCO SUMMARY
Multiple buckets are addressable by name, which is what separates this from a single hard-wired upload path.
Both tools turn on the same idea: configurations are named, list_oss_configs enumerates them, and upload_to_oss selects one by configName, so a client can move a file into the right bucket for the environment it is working in. Everything lives on the upload side — there is no listing, download or delete call in the set, and the file has to exist on the host running the server.
What it is
A two-tool upload server for Alibaba Cloud OSS, working from named bucket configurations supplied to it at start.
What you get
- File upload to OSS: upload_to_oss takes a local file path, an optional stored file name and target directory, and the configuration name that selects which bucket receives it.
- Configuration discovery: list_oss_configs returns the configurations available, which is what makes the configName on an upload something you can check rather than guess.
Requirements
An Alibaba Cloud OSS bucket and a named configuration carrying its region, access key id, access key secret, bucket and endpoint, supplied to the server at start rather than per call.
Setup effort
One command plus a key — npx oss-mcp --oss-config='{"default":{"region":"oss-cn-shenzhen","accessKeyId":"<YOUR_ACCESS_KEY_ID>","accessKeySecret":"<YOUR_ACCESS_KEY_SECRET>","bucket":"<YOUR_BUCKET>","endpoint":"oss-cn-shenzhen.aliyuncs.com"}}' --stdio, then supply credentials
USE CASES
01
Getting a file the client just produced into the right bucket
Check which named configurations the server was started with, then upload the local file under the one for that environment and the directory it belongs in.
2 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
upload_to_oss
Uploads a local file to Alibaba Cloud OSS, under the named configuration, target directory and stored file name given.
BEFORE YOU INSTALL
What to know first
Tools you get
2 tools when we connected.
Requires
npx on PATH
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 2 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx oss-mcp --oss-config='{"default":{"region":"oss-cn-shenzhen","accessKeyId":"<YOUR_ACCESS_KEY_ID>","accessKeySecret":"<YOUR_ACCESS_KEY_SECRET>","bucket":"<YOUR_BUCKET>","endpoint":"oss-cn-shenzhen.aliyuncs.com"}}' --stdioMCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"oss-mcp": {
"command": "npx",
"args": [
"oss-mcp",
"--oss-config='{\"default\":{\"region\":\"oss-cn-shenzhen\",\"accessKeyId\":\"<YOUR_ACCESS_KEY_ID>\",\"accessKeySecret\":\"<YOUR_ACCESS_KEY_SECRET>\",\"bucket\":\"<YOUR_BUCKET>\",\"endpoint\":\"oss-cn-shenzhen.aliyuncs.com\"}}'",
"--stdio"
]
}
}
}
