No user-submitted related servers found.
Scored across 20 tools
Most tools target distinct resource-action pairs (instances, volumes, scripts, SSH keys, config). The main ambiguity is between check_spot_availability, monitor_spot_availability, and deploy_spot_instance—especially since monitor can auto-deploy, blurring its boundary with deploy_spot_instance. create_startup_script and create_and_set_default_script also overlap slightly.
Tool names consistently follow verb_noun snake_case, e.g., list_instances, create_volume, attach_volume, delete_instance. Minor compounds like create_and_set_default_script and show_config vs list_* are acceptable deviations and don't create confusion.
With 20 tools, the server is on the heavier side for a cloud management MCP. While most tools have a purpose, some areas (script management, volume management, spot monitoring) could be consolidated without losing clarity, making the count feel slightly bloated.
Core instance lifecycle is covered (deploy, list, check, start, shutdown, delete), but there are notable gaps: volumes can be created/listed/attached/detached but not deleted; scripts can be created and set as default but not edited or deleted; SSH keys can be listed but not added or removed. There is also no on-demand instance creation separate from spot deployment.
