list_virtual_machinesLABSCO SUMMARY
Multiple environments, and a confirmation gate between them.
Handing an assistant this much reach over a cloud is only reasonable if the destructive half behaves differently from the rest, and here it does: the README counts 96 dangerous operations among its 477+ tools, and each requires a typed confirmation with the impact spelled out first. The per-environment credential blocks matter for the same reason — production and development are separate configurations, and which one is default is a deliberate setting rather than whatever was last used.
What it is
A broad CloudStack management server: virtual machines, storage and snapshots, networking and VPCs, accounts and domains, Kubernetes, templates and ISOs, quotas and autoscaling. It targets CloudStack 4.20 and, by the README's count, has 477+ tools across 32 API categories — the 53 listed here are the ones its documentation names — so most of what you would do through the CloudStack API is reachable by describing it instead of composing the call.
What you get
- Virtual machine lifecycle:
deploy_virtual_machine,start_virtual_machine,stop_virtual_machine,destroy_virtual_machineandlist_virtual_machines - Storage:
create_volume,delete_volume,create_snapshot,delete_snapshotandcreate_volume_from_snapshot - Networking and security:
list_networks,list_load_balancers,list_public_ip_addresses,list_port_forwarding_rules,create_security_groupanddelete_security_group - Inventory and capacity:
list_zones,list_hosts,list_templates,list_service_offeringsandlist_volume_metrics - A confirmation system the README says covers 96 dangerous operations — deletes, destroys, purges, scales and restarts are detected automatically
- Rich warnings on those operations, with severity and impact, and a typed confirmation such as "destroy permanently" before they run
Requirements
Node.js 18.0 or higher and CloudStack API credentials with the permissions you intend to use. Clone, npm install, npm run build (package cloudstack-mcp-server, version 3.0.5). Credentials go in the project's .env file — CLOUDSTACK_PROD_API_URL, CLOUDSTACK_PROD_API_KEY and CLOUDSTACK_PROD_SECRET_KEY, with an optional CLOUDSTACK_DEV_* set for a development environment and CLOUDSTACK_DEFAULT_ENVIRONMENT choosing which is active.
Setup effort
Build from source — git clone https://github.com/mozg31337/cloudstack-mcp-server.git
USE CASES
Standing up a virtual machine without the API syntax
Check the zones and service offerings available, then deploy.
Taking a snapshot before a risky change
Create the snapshot, and restore into a new volume if it goes wrong.
Auditing what is running across the cloud
List machines, hosts and volumes with their metrics in one pass.
Decommissioning safely
Stop the machine, then destroy it through the typed confirmation.
53 tools
Listed in project docs. Your client may show a different list.
deploy_virtual_machinestart_virtual_machinestop_virtual_machinereboot_virtual_machinedestroy_virtual_machineupdate_virtual_machinechange_service_offeringmigrate_virtual_machinescale_virtual_machinereset_vm_passwordget_vm_passwordadd_nic_to_vmremove_nic_from_vmrecover_virtual_machineexpunge_virtual_machinelist_volumescreate_volumeattach_volumedetach_volumedelete_volumeresize_volumemigrate_volumeextract_volumeupload_volumelist_volume_metricslist_snapshotscreate_snapshotdelete_snapshotcreate_volume_from_snapshotcreate_security_groupdelete_security_groupauthorize_security_group_ingressrevoke_security_group_ingresscreate_networkdelete_networkupdate_networkrestart_networklist_network_offeringsassociate_ip_addressdisassociate_ip_addresslist_public_ip_addressesenable_static_natdisable_static_natcreate_port_forwarding_ruledelete_port_forwarding_rulelist_port_forwarding_ruleslist_networkslist_zoneslist_hostslist_service_offeringslist_templatesget_cloudstack_infoBEFORE YOU INSTALL
What to know first
Tools you get
53 tools named in the project's documentation.
Requires
- Node.js Version 18.0
- CLOUDSTACK_PROD_API_URL in your environment
- CLOUDSTACK_PROD_API_KEY in your environment
- CLOUDSTACK_PROD_SECRET_KEY in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
git clone https://github.com/mozg31337/cloudstack-mcp-server.git
cd cloudstack-mcp-server
npm install
npm run build
cp .env.example .envEdit .env with your actual credentials:
CLOUDSTACK_PROD_NAME="Production CloudStack"
CLOUDSTACK_PROD_API_URL="<YOUR_CLOUDSTACK_URL>/client/api"
CLOUDSTACK_PROD_API_KEY="<YOUR_CLOUDSTACK_PROD_API_KEY>"
CLOUDSTACK_PROD_SECRET_KEY="<YOUR_CLOUDSTACK_PROD_SECRET_KEY>"
CLOUDSTACK_DEFAULT_ENVIRONMENT="default"Add the MCP server to your Claude Desktop configuration, then restart Claude Desktop.
MCP Clients
Claude Desktop
{
"mcpServers": {
"cloudstack": {
"command": "node",
"args": [
"<YOUR_PATH_TO_CLOUDSTACK_MCP_SERVER>/dist/server.js"
]
}
}
}