Alibaba Cloud OSS MCP integration for AI agents.
Connect AI agents to Alibaba Cloud OSS through 7 structured actions, including download object, delete object, and generate presigned url. Review authenticat…
- ACTION CONTRACTS
- 7
- AUTHENTICATION
- Custom credentials
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Alibaba Cloud OSS integration exposes
The Alibaba Cloud OSS Agent App exposes 7 provider-backed actions for storage and developer tools work. Its current contract lets an authorized agent download one oss object into local transit file storage, delete one oss object, and generate a pre-signed oss url for reading, uploading, or deleting one object. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses Custom credentials. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Alibaba Cloud OSS account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Alibaba Cloud OSS capabilities.
Showing 7 of 7 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
download_objectREADDownload one OSS object into local transit file storage.
INPUTS: bucket / objectKey / endpoint / versionId / fileName
delete_objectHIGH IMPACTDelete one OSS object.
INPUTS: bucket / objectKey / endpoint / versionId
generate_presigned_urlREVIEWGenerate a pre-signed OSS URL for reading, uploading, or deleting one object.
INPUTS: bucket / objectKey / endpoint / method / expiresSeconds
head_objectREVIEWFetch structured metadata for one OSS object.
INPUTS: bucket / objectKey / endpoint / versionId
list_bucketsREADList OSS buckets visible to the connected Alibaba Cloud credential.
INPUTS: endpoint / prefix / marker / maxKeys
list_objectsREADList objects in an OSS bucket with the ListObjectsV2 API.
INPUTS: bucket / endpoint / prefix / delimiter / continuationToken
put_objectREVIEWUpload one object to OSS from a public URL, plain text, or base64-encoded content.
INPUTS: bucket / objectKey / endpoint / sourceUrl / contentText
INPUT CONTRACTS
Know what the action needs before it runs.
download_object
bucketOPTIONAL- The OSS bucket name.
objectKeyREQUIRED- The complete OSS object key. Slashes are preserved as key delimiters.
endpointOPTIONAL- The OSS endpoint, for example `oss-cn-hangzhou.aliyuncs.com`. Actions can omit it to reuse the connected default endpoint.
versionIdOPTIONAL- The optional object version ID.
fileNameOPTIONAL- An optional filename override for the local transit file.
delete_object
bucketOPTIONAL- The OSS bucket name.
objectKeyREQUIRED- The OSS object key.
endpointOPTIONAL- The OSS endpoint, for example `oss-cn-hangzhou.aliyuncs.com`. Actions can omit it to reuse the connected default endpoint.
versionIdOPTIONAL- The optional object version ID.
generate_presigned_url
bucketOPTIONAL- The OSS bucket name.
objectKeyREQUIRED- The OSS object key.
endpointOPTIONAL- The OSS endpoint, for example `oss-cn-hangzhou.aliyuncs.com`. Actions can omit it to reuse the connected default endpoint.
methodOPTIONAL- The HTTP method that the signed URL should allow.
expiresSecondsOPTIONAL- How long the signed URL remains valid, in seconds.
head_object
bucketOPTIONAL- The OSS bucket name.
objectKeyREQUIRED- The OSS object key.
endpointOPTIONAL- The OSS endpoint, for example `oss-cn-hangzhou.aliyuncs.com`. Actions can omit it to reuse the connected default endpoint.
versionIdOPTIONAL- The optional object version ID.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Download Object
Download one OSS object into local transit file storage. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
download_objectControl Delete Object
Delete one OSS object. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
delete_objectVerify with List Buckets
List OSS buckets visible to the connected Alibaba Cloud credential. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_bucketsSAFETY BOUNDARY
Operate Alibaba Cloud OSS with explicit limits
- Authorize Alibaba Cloud OSS with Custom credentials and grant only the provider access required by the selected actions.
- 1 action is change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_object` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Alibaba Cloud OSS rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Alibaba Cloud OSS task completed successfully.
CONNECTION MODEL
Custom credentials
Alibaba Cloud OSS uses Custom credentials. Connection requirements and availability are determined by the provider and the Working Machines deployment.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 3
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 3
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Alibaba Cloud OSS.