Deployado
Related Servers
Alternatives to Deployado
No user-submitted related servers found.
Related Servers
AlicenseAqualityCmaintenanceEnables AI coding tools to deploy and manage apps, managed databases, and GPU pods, with tools for logs, metrics, diagnostics, scaling, rollbacks, domains, and environment variables.33MIT- AlicenseNot gradedqualityBmaintenanceEnables an AI agent to inspect and manage hosted applications, including projects, environments, previews, logs, domains, health, and backups, with explicit confirmation required for deploys, deletions, and production changes.MIT

cmo-studioofficial
AlicenseNot gradedqualityCmaintenanceEnables deploying and managing apps with hosting, logs, rollbacks, environment variables, domains, Postgres databases, file storage, and transactional email. It also supports SQL console operations, database imports, and support requests.MIT- AlicenseNot gradedqualityCmaintenanceEnables AI agents to build and deploy an app from a GitHub repository to a managed live server and then operate it — logs, captured errors, health checks, managed Postgres, secrets, custom domains, email authentication, and Stripe checkout links. It also exposes safe, read/write-labelled tools so agents can rebuild, start/stop, and inspect projects without ever editing source code.MIT

Create app hostingofficial
AlicenseNot gradedqualityCmaintenanceEnables AI assistants to create projects, deploy files, container images, or Git repositories, attach domains, set write-only secrets, add Postgres, read logs, metrics, and failure summaries, and roll back.Apache 2.0
Roar AI MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI assistants to deploy and manage hosted apps from git repos, read logs, add Postgres databases and domains, manage API keys and budgets, and send requests to 200+ AI models. Connects over remote Streamable HTTP with OAuth sign-in, so users need no API keys, installs, or local server.MIT
TDQS
Scored across 58 tools
Most tools target distinct resources and actions, and descriptions clarify the deployment/release/doctor triage cluster. The main weak spot is the near-duplicate pair deployado_get_build_logs and deployado_release_logs, which both fetch the Docker build transcript for a release, forcing an arbitrary choice.
Every tool uses the deployado_ prefix with a consistent snake_case verb_noun pattern (get_app, create_project, list_databases, run_backup). Even the singular nouns and the one-verb deploy_blueprint fit the pattern predictably.
58 tools is far beyond a well-scoped set and includes redundant log fetchers. The domain (apps, projects, deployments, databases, services, domains, cron, backups) justifies a large surface but not this many; it is heavy enough to burden selection.
Lifecycle coverage is strong: CRUD for apps, projects, databases, cron jobs, env vars, plus deploy/rollback, exec, logs, backups, and diagnostics. Minor gaps remain, e.g. no domain update (only add/remove/set-primary) and no database resize/rename operations.