Cloady
OfficialRelated Servers
Alternatives to Cloady
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables deploying and managing projects across AWS, Google Cloud, Azure, DigitalOcean, Hetzner, and Vercel directly from Claude Code, with tools for instance lifecycle, domains, environment variables, backend services, databases, webhooks, and GitHub integration.89 npm3MIT
- AlicenseBqualityBmaintenanceEnables AI assistants to manage a self-hosted PaaS by listing projects and services, reading deployment and container logs, and deploying, restarting, or updating environment variables for applications and compose services.322Apache 2.0
- AlicenseDqualityFmaintenanceProvides programmatic and CLI tools for managing Coolify deployments, allowing users to control applications, services, databases, and infrastructure through natural language or command line.1030 npm7Good Luck With That Public
- AlicenseBqualityDmaintenanceEnables AI assistants to interact with Coolify for complete infrastructure management including applications, databases, servers, deployments, and team operations. Provides 100% API coverage with 64 tools for managing the entire Coolify ecosystem through natural language.188 npm6MIT

@vertracloud/mcpofficial
AlicenseBqualityBmaintenanceEnables AI assistants to operate Vertra Cloud resources through the public API: deploy and manage applications, view logs and metrics, create and restore snapshots, and administer databases and environment variables.139672 npm2MIT- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to manage cloud infrastructure through natural language by providing a unified interface to the Dokploy platform. Supports Docker containers, applications, databases, domains, monitoring, and deployment operations through conversational commands.50 npm1-
TDQS
Scored across 160 tools
The 160-tool surface covers many subdomains, and most tools have distinct scopes documented in detail, but several families are easy to confuse: getStatusPage vs getPublicStatus, queryAppMetrics vs streamAppMetrics vs queryAppMetricsRange vs queryWorkspaceMetrics, listWorkspaceDomains vs listAppDomains vs listDnsRecords, and createSshSession vs getSshSession. Descriptions usually resolve the ambiguity, so boundaries are mostly clear but not effortless.
Almost all names are camelCase verb-first (list..., get..., create..., update..., delete..., stream..., read..., query...). The convention is consistent across 160 tools, with only natural verb variety rather than style mixing.
160 tools is far beyond the 3-15 well-scoped range and even beyond the 25+ 'too many' threshold; the platform is broad, but this is an extreme surface for one MCP server. Each subdomain could be split into separate servers.
Coverage is unusually broad: workspace/app lifecycle, deploys, domains/DNS, variables, volumes/backups, billing, support, observability, git, database, mail, alerts, and integrations. Minor gaps remain, such as no obvious standalone getApp/listApps tool, but getWorkspace appears to expose app details and most workflows have a path.