UpCloud MCP by usefulapi

Each tool targets a distinct resource and action: get_server vs list_servers vs modify_server vs start/stop/restart_server are cleanly separated, and every list_* / get_* maps to a unique resource. Descriptions reinforce boundaries (e.g. list_servers defers IPs/disks to get_server), so misselection is unlikely.

All 22 tools follow a strict upcloud_{verb}_{noun} snake_case pattern with a consistent namespace prefix. Verbs are limited to a predictable set (get, list, create, modify, start, stop, restart) and resource nouns are reused consistently.

22 tools is on the heavier side but each maps to a genuine UpCloud resource type (servers, storage, networks, databases, kubernetes, load balancers, object storage, billing, audit, plans, prices, zones) plus server lifecycle verbs. The set is broad but not padded with redundant tools.

Coverage is strongly read-oriented (list_* / get_* across many resources) with mutations limited to server power state, server metadata, and storage backup. Notable gaps: no create_server, storage, network, database, kubernetes, load balancer, or object storage, and no delete/terminate anywhere, so provisioning and teardown workflows will fail despite thorough inventory/audit coverage.