Cloud Use is a capability of Qoder Cloud Agents that lets a cloud-resident agent operate your Alibaba Cloud resources under a governed identity, completing tasks end-to-end in the cloud.
This page walks you through setup and a few typical cloud-use scenarios.
Setup takes two steps: in the console, authorize the Alibaba Cloud OpenAPI MCP via OAuth, and import official Alibaba Cloud skills from the Skill marketplace as needed. After that, in a cloud session the agent uses a platform-injected machine identity to call the Alibaba Cloud OpenAPI through MCP and complete tasks with those skills. Because the agent runs in the cloud, it can run long-term, be triggered in real time by events, and every cloud action is recorded server-side.
Typical use: ops and incident response, data analytics, data processing, and cost governance — tasks that need an agent to run long-term, trigger in real time, and operate Alibaba Cloud resources under a governed identity.
Cloud Use operates the cloud through the Alibaba Cloud OpenAPI MCP, authenticated with OAuth in the console. The five steps below are all done in the console.
Step 1 · Get your MCP URL
Open the MCP onboarding page of the Alibaba Cloud OpenAPI portal, and choose the domain for your account's site:
Step 3 · Create a Vault and authorize in the console
In the Cloud Agents console → Vault → create a credential:
In the console under Skills → Create → Import from Skill marketplace:
Incident Response
Q: How is this different from using a local Coding Agent + Alibaba Cloud MCP?
A: With Cloud Use, the agent runs in the cloud, so it can run 24/7 long-term and be triggered in real time by events (such as alert webhooks) without depending on your local machine being online. Cloud operations run under an authorized machine identity, with credentials hosted and injected by the platform — they never touch your local machine. Every cloud action is recorded server-side and auditable.
Q: During authorization I see "application not authorized to install, please re-initiate the authorization flow".
A: Go back to Setup Step 2 and confirm the OpenAPI MCP Server official app is installed in Alibaba Cloud RAM under OAuth Applications (Public Preview), then re-initiate OAuth.
Q: Where do I find the bills for the Alibaba Cloud usage?
A: Cloud Use consumption is billed to whichever Alibaba Cloud account you authorized — the Alibaba Cloud account that completed the OAuth authorization for the MCP is the one that incurs the API calls and resource consumption, and its bills live under that account. View them in the Billing Center of the corresponding Alibaba Cloud account.
Q: Are there differences between the China site and the International site?
A: Yes. The Alibaba Cloud MCP onboarding portal and the RAM console are each split by China site / International site (see Step 1 for the onboarding page and Step 2 for the RAM console). Pick the domain that matches your account's site.
Q: Can multiple sessions of the same agent share the same authorization?
A: Yes. Authorization and connection live in the Vault; agents just reference (mount) it. Configure it once and reuse it in many places.
1. How it works
Setup takes two steps: in the console, authorize the Alibaba Cloud OpenAPI MCP via OAuth, and import official Alibaba Cloud skills from the Skill marketplace as needed. After that, in a cloud session the agent uses a platform-injected machine identity to call the Alibaba Cloud OpenAPI through MCP and complete tasks with those skills. Because the agent runs in the cloud, it can run long-term, be triggered in real time by events, and every cloud action is recorded server-side.
Typical use: ops and incident response, data analytics, data processing, and cost governance — tasks that need an agent to run long-term, trigger in real time, and operate Alibaba Cloud resources under a governed identity.
2. Connect to Alibaba Cloud (OAuth · in the console)
Cloud Use operates the cloud through the Alibaba Cloud OpenAPI MCP, authenticated with OAuth in the console. The five steps below are all done in the console.
Prerequisite: you have an Alibaba Cloud account with permission to install OAuth Applications (Public Preview) in RAM.
- China site: https://api.aliyun.com/mcp
- International site: https://api.alibabacloud.com/mcp
- China site: https://ram.console.aliyun.com/applications?activeTab=ThirdParty
- International site: https://ram.console.alibabacloud.com/applications?activeTab=ThirdParty
This is a prerequisite for OAuth. If the official app isn't installed, the authorization page fails with "application not authorized to install".
- Credential type:
MCP OAuth - MCP server: select the pinned "Alibaba Cloud · Cloud Use" from the dropdown (or choose "Custom URL" and paste the address from Step 1). If you're unsure of the URL, click "Get the Alibaba Cloud Cloud Use MCP URL" and follow the guide.
3. Import cloud-use skills
In the console under Skills → Create → Import from Skill marketplace:
- Pick the pinned "Cloud Use" category to see the curated cloud-use skills;
- Or search for official Alibaba Cloud skills (e.g., RAM Permission Diagnosis, DataWorks Data Development, Quick BI NL2SQL) and import them;
- After Import, the skill appears in your Skills list and can be used in your agent right away.
4. Typical scenarios
Incident Response
- Outcome: on alert → locate root cause → controlled mitigation → fix PR.
- Key permissions: logs / monitoring read-only
allow; restart / scale / shift traffic (mitigation)ask; delete / releasedeny. - Recommended skills: RAM Permission Diagnosis & Policy Generator, CloudMonitor 2.0 Lifecycle Management, Elasticsearch Cluster Diagnosis & Repair.
- Trigger: event-driven (alert webhook, real time).
- Outcome: natural-language question → explore schema → generate and run SQL → chart → attribution explanation.
- Key permissions: query / run SQL (read-only)
allow; write operationsdeny. - Recommended skills: Smart-Q Data Analytics (Quick BI), NL2SQL Engine (DMS, 60+ sources), Data Visualization.
- Trigger: real-time Q&A; optional daily digest at 08:00.
- Outcome: read source → rule-based clean / transform / aggregate → write to target dataset → validate row count and schema.
- Key permissions: read source
allow; write back to target table / OSSask; delete source datadeny. Tasks must be idempotent and re-runnable. - Recommended skills: DataWorks Data Development, ClickHouse Data Migration, MaxCompute Metadata Analysis.
- Trigger: daily batch at 02:00 (cron configurable).
- Outcome: pull bills and utilization → top cost items, each with "estimated monthly savings + a one-line fix".
- Key permissions: bills / utilization (read-only)
allow; stop idle / downsize / lifecycleask. - Recommended skills: EMR Cluster Lifecycle Management (cost tags), MaxCompute Metadata (task cost tracking), DAS Database Autonomy.
- Trigger: daily at 09:00 (cron configurable).