American Cloud MCP Server
OfficialRelated Servers
Alternatives to American Cloud MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server for Kvindo Cloud that lets AI clients list, inspect, create, update, and delete cloud resources (VMs, volumes, Kubernetes, etc.) via natural language. Read-only by default, with write/delete operations gated by explicit opt-in environment variables.13 npm1MIT
- AlicenseAqualityDmaintenanceA read-only MCP server for Akamai Cloud (Linode) that lets users ask plain-language questions about their account, including inventory, pricing, GPU availability, and account limits.3773 PyPI2Apache 2.0
- AlicenseNot gradedqualityBmaintenanceA remote Streamable HTTP MCP server that lets web clients like Claude.ai and ChatGPT manage cloud machines with OAuth login — creating, starting, pausing and deleting machines, running commands, reading and writing files, managing snapshots and public ports, and driving an optional Linux desktop via screenshots and input actions. Long-running work can be backgrounded and operations polled, so browser-based clients stay within their timeouts.MIT
- AlicenseBqualityCmaintenanceMCP Server for full Easypanel control via Claude Code, Cursor, and Claude Desktop. Provides 37 tools for deploy, logs, env vars, domains, databases, and monitoring with built-in safety guards.57309 npm4MIT
- AlicenseAqualityCmaintenanceEnables MCP-compatible clients like Claude Desktop, Claude Code, Codex, and local-model hosts to inspect Proxmox VE clusters, nodes, VMs, containers, storage, snapshots, and tasks, with opt-in write operations for starting, stopping, cloning, backing up, and migrating guests. Read-only by default, it supports both stdio and Streamable HTTP transports.14MIT
- AlicenseNot gradedqualityCmaintenanceEnables managing a self-hosted Coolify PaaS from Claude, Cursor, or any MCP client through 45 tools for deploying, rolling back, debugging, and operating applications, databases, services, projects, and environments in plain English. Destructive operations pause for human confirmation and secrets stay masked.MIT
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.