The OOS tools take a list of instance IDs, so starting a group of machines, rotating their passwords or swapping their system disks is a single call. Metrics, inventory and deployment sit behind the same access key, which puts the question — is this instance loaded — and the action — restart it — in the same session.
Alibaba Cloud operations in 40 tools: OOS batch actions over ECS and RDS, CloudMonitor metric reads, OSS bucket management, ECS/VPC/RDS inventory queries, and three tools that act on the local machine to prepare a deployment.
- Batch lifecycle control over ECS instances — create, start, stop, reboot, reset passwords, replace the system disk — taking an instance ID list and a region
- The same batch start, stop and reboot operations against RDS instances
- Cloud Assistant commands run across many ECS instances at once, for jobs like application management and resource tagging
- CloudMonitor metrics per instance: CPU utilization, one-, five- and fifteen-minute load averages, memory used and utilization, and disk total, used and utilization
- Application deployment through OOS CodeDeploy, with the previous deployment's details and the current status of an application group
- Inventory across ECS, VPC and RDS — instances, regions, zones, images, security groups, account quotas, zone stock, VPCs, vSwitches and database instances
- OSS buckets listed, created and deleted, and the objects inside a bucket listed
- Local-side preparation: a directory listed, a project's stack identified as npm, Python, Java, Go or Docker, and a shell script run
An Alibaba Cloud access key — ALIBABA_CLOUD_ACCESS_KEY_ID and ALIBABA_CLOUD_ACCESS_KEY_SECRET — and uv on your PATH, which resolves the Python runtime through UV_PYTHON. LOCAL_RunShellScript runs on the machine hosting the server, not on an ECS instance.
One command plus a key — uvx alibaba-cloud-ops-mcp-server@latest, then supply credentials