American Cloud MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AMERICANCLOUD_API_URL | No | API base URL override | |
| AMERICANCLOUD_API_CLIENT_ID | Yes | API client ID (X-API-Client-ID) | |
| AMERICANCLOUD_API_CLIENT_SECRET | Yes | API client secret (X-API-Client-Secret) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
American Cloud infrastructure management — one tool per API operation across compute, storage, networking, Kubernetes, databases, WordPress, and DNS.
Getting started:
Call get_server_info to see the version, enabled service groups, and whether the server is read-only.
Discover before creating: list_* tools (e.g. list_regions, list_images, list_vm_packages) return the labels and IDs that create_* tools require.
Preview cost before provisioning: each get_cost_estimate_* takes the same arguments as its create_* tool and charges nothing.
Resources often provision asynchronously — poll the matching get_* tool until the status settles.
Connecting to a VM:
The default SSH login user on Linux images is cloud: ssh -i cloud@. Connect as cloud unless the user names a different user, for example root.
Set up an SSH key before create_vm, and pass its name in create_vm's keypairs argument. Key login needs no VM password. Use a key from list_ssh_keys, or register a public key with create_ssh_key.
If you have a shell, register the host's own public key (for example ~/.ssh/id_ed25519.pub) with create_ssh_key, so the host logs in with the key it already has. Ask the user before you run ssh-keygen. If you have no shell, ask the user for a public key and register it. Let create_ssh_key generate a pair only when the user asks for one, and say that the private key then stays in this chat.
Open port 22 when you create the VM: set create_vm's networkAccess.inboundPorts to [{port: 22, protocol: "TCP"}], with sourceCidr set to the user's address when you know it. On an existing network, check that its public IP has a port forwarding rule and a firewall rule for port 22; create_port_forwarding_rule and create_firewall_rule add them.
The ipAddress of get_vm is the private address on the VM's network. The public IP comes from list_public_ips_by_isolated_network or list_public_ips_by_vpc for the network of the VM.
Kubernetes cluster nodes also use the cloud user, with the key from create_kubernetes_cluster's keypair argument. Node SSH is on the cluster's public IP at port 2222 for the first node, 2223 for the next, and so on: ssh -p 2222 cloud@.
A VM password (from create_vm or reset_vm_password) belongs to the cloud user.
If SSH is unavailable, open a browser console with create_vm_console.
Inside a VM:
No tool runs a command inside a VM. The tools manage the account: they create, change, power, resize and delete resources. They do not run software on them.
If you have a shell, use it: find the public IP as above, then ssh cloud@ and run the command yourself.
If you have no shell, say so, and offer the alternatives: a cloud-init script in create_vm's userdata argument configures a new VM on first boot, and create_vm_console gives the user a browser console for a running VM.
Safety: read-only by default. Create/modify/delete tools, and the tools that return a secret (access keys, database passwords, kubeconfig), appear only when the server is started with --allow-writes; if they're missing and the user wants to make changes or read a secret, they must restart with that flag. Tools whose description starts with ⚠️ DESTRUCTIVE cause irreversible loss — confirm with the user before calling them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_server_infoA | Describe this American Cloud MCP server: version, pinned SDK version, API endpoint, the kind of credential in use, enabled service groups, and whether it is running in read-only mode. Useful to confirm configuration before managing resources. |
| list_vmsA | List the virtual machines in your American Cloud account, one page at a time, with their IDs, names, status, region, and IP addresses. |
| get_vmA | Get one virtual machine by ID: status, specs, IP address, network, and image details. The ipAddress is the private address on the VM's network; the public IP comes from list_public_ips_by_isolated_network or list_public_ips_by_vpc for that network. To connect over SSH, log in at the public IP as the default user cloud, unless the user names a different one. |
| get_vm_metricsB | Get CPU, memory, network, and disk usage metrics for a VM over the last N hours. |
| get_cost_estimate_vmA | Preview the price of a VM configuration without creating anything. Takes the same arguments as create_vm and returns hourly/monthly cost breakdowns — use this before create_vm when cost matters. |
| list_vm_packagesA | List the available VM packages (compute tiers) with their labels, CPU/memory/disk limits, and zones. Package labels are required by create_vm and get_cost_estimate_vm. |
| get_vm_packageA | Get one VM package by its UUID, including CPU/memory/disk limits. |
| get_vm_package_by_labelA | Get one VM package by its public label (e.g. "standard-custom"), including CPU/memory/disk limits. |
| list_imagesA | List the operating system images available for VM creation, optionally filtered by OS and version. Image labels are required by create_vm and reinstall_vm. |
| get_imageA | Get one OS image by its UUID (from list_images), including its label and OS details. |
| get_image_by_labelA | Get one OS image by its public label (e.g. "ubuntu-24.04-050826"). |
| list_regionsA | List the regions where infrastructure can be provisioned. Region labels are required by create_vm and most create tools. |
| get_regionA | Get one region by its UUID (from list_regions), including its label and availability. |
| get_region_by_labelA | Get one region by its public label (e.g. "us-west-0"). |
| list_ssh_keysA | List the SSH key pairs registered in your account. Key names are used by create_vm's keypairs argument. |
| list_block_storage_volumesA | List block storage volumes in your account, optionally filtered to a VM. Returns IDs, sizes, regions, and attachment state. |
| get_block_storage_volumeA | Get one block storage volume by ID: size, region, and attachment state. |
| get_cost_estimate_block_storageA | Preview the price of a block storage volume configuration without creating it. Takes the same arguments as create_block_storage_volume. |
| list_block_storage_snapshotsB | List the snapshots taken of a specific block storage volume. |
| list_snapshotsB | List all volume snapshots in your account with their IDs, source volumes, and types. |
| get_snapshotB | Get one snapshot by ID: source volume, type, size, and creation time. |
| get_cost_estimate_snapshotA | Preview the price of a snapshot without creating it. Takes the same arguments as create_snapshot. |
| list_object_storage_unitsA | List your S3-compatible object storage units, optionally with usage figures. A unit contains buckets and has its own access keys. A null maxBuckets or limitKb means unlimited. |
| list_object_storage_bucketsC | List the buckets within an object storage unit. |
| get_cost_estimate_object_storageA | Get the metered pricing for object storage (per-GB rate and minimums). Takes no arguments — object storage is billed by actual usage. |
| list_kubernetes_versionsA | List the available Kubernetes versions. Pass current_version to get only valid upgrade targets from a running cluster's version. |
| list_kubernetes_packagesA | List the available Kubernetes node packages (sizing/pricing tiers) for cluster creation. |
| list_kubernetes_clustersB | List the Kubernetes clusters in your account with their IDs, status, version, and node counts. |
| get_kubernetes_clusterA | Get one Kubernetes cluster by ID. Pass details=true for full node and status information. |
| get_cost_estimate_kubernetesA | Preview the price of a Kubernetes cluster configuration without creating it. Takes the same arguments as create_kubernetes_cluster. |
| list_isolated_networksA | List standalone isolated (single-tier private) networks in your account. VPC tier subnets are listed separately via get_vpc_network. |
| get_isolated_networkA | Get one standalone isolated network by ID, including its CIDR and status. If the ID belongs to a VPC tier subnet (e.g. from a VM in a VPC), use get_vpc_tier instead. |
| list_vpc_networksB | List Virtual Private Cloud networks, which contain multiple tier subnets. |
| get_vpc_networkB | Get one VPC network by ID, including its tiers and status. |
| get_cost_estimate_vpc_networkA | Preview the price of a VPC configuration without creating it. Same arguments as create_vpc_network. |
| get_vpc_tierA | Get one tier (subnet) of a VPC, including its CIDR, gateway, ACL, status, and creation date. Use the tier IDs from get_vpc_network. |
| list_public_ipsB | List the public IP addresses allocated to your account. |
| list_public_ips_by_isolated_networkC | List the public IPs allocated within a specific isolated network. |
| list_public_ips_by_vpcB | List the public IPs allocated within a specific VPC. |
| get_public_ipA | Get one public IP by ID, including its NAT configuration. |
| get_cost_estimate_public_ipA | Get the price of a public IP address. Takes no arguments. |
| list_firewall_rulesB | List inbound firewall rules on a public IP. |
| list_port_forwarding_rulesB | List port forwarding rules on a public IP. |
| list_load_balancer_rulesC | List load balancer rules on a public IP. |
| list_load_balancer_instancesB | List the VMs assigned (or assignable) to a load balancer rule. |
| list_egress_rulesA | List outbound (egress) traffic rules across your isolated networks. |
| list_egress_rules_by_networkA | List the egress rules for a specific isolated network. |
| get_egress_ruleA | Get one egress rule by ID (from list_egress_rules), including its protocol, ports, and CIDRs. |
| list_network_acl_listsC | List network ACL lists, which are applied to VPC tiers. |
| list_network_acl_lists_by_vpcB | List the ACL lists belonging to a specific VPC. |
| get_network_acl_listB | Get one network ACL list by ID. |
| list_network_acl_rulesC | List the rules within a network ACL list. |
| get_network_acl_ruleC | Get one network ACL rule by ID. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 53 tools
Most tools target clearly distinct resources and actions, with scoped list variants (by VPC, by isolated network) and ID-vs-label lookups clarified in descriptions. A few pairs overlap conceptually, such as list_snapshots vs list_block_storage_snapshots and the various list_public_ips variants, but the descriptions make the boundaries understandable.
Tool names consistently use snake_case verb_noun patterns: list_*, get_*, and get_cost_estimate_* followed by the resource. Variants such as *_by_label, *_by_vpc, and *_by_isolated_network are applied predictably across resource groups.
The domain is broad, but 53 tools is too large for a single MCP surface and creates a heavy selection burden for an agent. Many tools are read-only list/get variants, so the count feels over-scoped rather than each tool being essential.
The server provides extensive read-only inspection and cost-estimation coverage, but there are no create, update, delete, or lifecycle action tools despite descriptions referencing create_vm, create_snapshot, create_vpc_network, reinstall_vm, and similar operations. This leaves major gaps for actual cloud resource management.