Deployado
Related Servers
Alternatives to Deployado
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables 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 gradedqualityBmaintenanceEnables 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.5 npmApache 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- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to check repository deploy readiness, deploy apps to your own cloud (AWS, Google Cloud, Azure, DigitalOcean), and migrate apps from platforms like Heroku, Railway, Render, or Vercel with rollback.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding assistants to deploy and manage compatible web apps, isolated Postgres databases, and project file storage, while inspecting build logs, runtime errors, and usage through an OAuth-authenticated remote MCP connection.MIT

@vertracloud/mcpofficial
AlicenseBqualityAmaintenanceEnables 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.127434 npm2MIT
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.