Deployado
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Deployado Deploy the api app and then show me the build logs"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
deployado-mcp
Model Context Protocol server for Deployado. It lets AI agents (Claude Code, Claude Desktop, Cursor and any other MCP client) deploy and roll back apps, read build and runtime logs, diagnose broken apps, and manage env vars, databases, domains, cron jobs, services and backups.
Docs: https://deployado.com/en/docs/mcp
Requirements
Node.js 22 or newer (
npxcomes with it). Node 20 reached end of life in April 2026.A Deployado API token: Settings → API Tokens (https://deployado.com/settings/api-tokens). This is separate from the CLI's
deployado auth login.
Related MCP server: Roar AI MCP Server
Install
Claude Code
claude mcp add deployado --scope user --env DEPLOYADO_API_TOKEN=<your-token> -- npx -y deployado-mcp--scope user makes it available in every project; drop it to add it only to
the current one. Check it with claude mcp list.
Claude Desktop, Cursor and other clients
Add to the client's MCP configuration (claude_desktop_config.json,
~/.cursor/mcp.json, …):
{
"mcpServers": {
"deployado": {
"command": "npx",
"args": ["-y", "deployado-mcp"],
"env": {
"DEPLOYADO_API_TOKEN": "your-token-here"
}
}
}
}Restart the client after editing the file.
Configuration
Variable | Required | Description |
| Yes | API token from Settings → API Tokens |
| No | API base URL (default |
npx deployado-mcp --version prints the installed version.
Safety annotations
Every tool declares MCP tool annotations:
read-only tools (list_*, get_*, logs, doctor) are marked readOnlyHint,
and anything that deletes, overwrites or takes something down (deletes,
rollback, restore, set_env, exec, stopping a service, …) is marked
destructiveHint, so clients can ask for confirmation before running them.
Tools
Diagnostics
deployado_doctor— full diagnostic checklist for one app (deployment, latest build, server, instances, HTTP probe, env). Start here when an app misbehaves.
Account
deployado_whoami— current account, user and token
Apps
deployado_list_apps,deployado_get_appdeployado_create_app,deployado_update_app,deployado_delete_appdeployado_deploy— trigger a deployment (returns arelease_id)deployado_rollback— roll back to a previous releasedeployado_get_logs— runtime logs of the running container
Releases & builds
deployado_list_releases,deployado_get_releasedeployado_get_build_logs,deployado_release_logs— build transcript (in-progress or finished)
Deployments
deployado_list_deployments,deployado_get_deployment,deployado_current_deployment
Environment variables
deployado_list_env,deployado_set_env,deployado_delete_env
Servers
deployado_list_servers,deployado_get_server
Projects
deployado_list_projects,deployado_get_projectdeployado_create_project,deployado_update_project,deployado_delete_project
Databases (managed PostgreSQL)
deployado_list_databases,deployado_get_databasedeployado_create_database,deployado_delete_databasedeployado_connect_database,deployado_disconnect_database
Exec
deployado_exec— run a command inside an app's container (60 s timeout)
Blueprints
deployado_validate_blueprint,deployado_deploy_blueprint
Domains
deployado_list_domains,deployado_add_domain,deployado_remove_domaindeployado_set_primary_domain,deployado_verify_domains
Cron jobs
deployado_list_cron_jobs,deployado_create_cron_job,deployado_update_cron_jobdeployado_delete_cron_job,deployado_run_cron_job
Services (marketplace)
deployado_list_service_templates,deployado_list_services,deployado_get_servicedeployado_install_service,deployado_start_service,deployado_stop_service,deployado_restart_service
Backups
deployado_list_backup_targets,deployado_create_backup_target,deployado_get_backup_targetdeployado_run_backup,deployado_restore_backup
Prompts and resources
Prompt
deployado_status— overview of apps, servers and databasesResources
deployado://appsanddeployado://servers
Development
npm install
npm run build
npm test # stdio smoke test: handshake, listings, annotations
npm run dev # run from source with tsxWhen adding a tool, add its entry to src/tools/annotations.ts — npm test
(and therefore npm publish) fails otherwise.
Available Tools
58 toolsdeployado_add_domainAIdempotent
Add a custom domain to an app. You must configure DNS (CNAME or A record) separately.
Inputs: app_id (required), hostname (required).
deployado_connect_databaseAIdempotent
Connect an app to a database. This injects the connection URL as an environment variable into the app.
Inputs: app_id (required), database_id (required), driver, use_ssl, +1 more.
deployado_create_appA
Create a new app in a project.
IMPORTANT: Apps with a repository_url are built using Docker. The repository MUST contain a Dockerfile (at dockerfile_path, default "Dockerfile" relative to build_context).
For static websites (HTML/CSS/JS), add a simple Dockerfile: FROM nginx:alpine COPY . /usr/share/nginx/html EXPOSE 80
Key parameters:
repository_url: Git repo URL (HTTPS). Required for repo-based apps.
dockerfile_path: Path to Dockerfile relative to build_context (default: "Dockerfile").
build_context: Subdirectory where Docker build runs, relative to repo root (default: "."). Use this when your site is in a subfolder (e.g. "website").
port: The port your app listens on inside the container. For nginx use 80, for Node.js typically 3000 or 8080.
branch: Git branch to build from (default: "main").
Inputs: name (required), project_id (required), port, branch, +3 more.
deployado_create_backup_targetB
Create a new database backup target. Backups are stored in S3.
Inputs: name (required), db_host (required), db_name (required), db_user (required), +5 more.
deployado_create_cron_jobC
Create a new cron job for an app.
Inputs: name (required), app_id (required), command (required), cron_expression (required), +2 more.
deployado_create_databaseA
Create a new managed PostgreSQL database. The database name will be auto-prefixed with your account slug.
Inputs: name (required), server_id, project_id.
deployado_create_projectC
Create a new project in your Deployado account.
Inputs: name (required), description, default_branch, repository_url.
deployado_current_deploymentARead-onlyIdempotent
Get the currently active deployment for an app.
Inputs: app_id (required).
deployado_delete_appADestructive
Permanently delete an app and all its deployments, releases, and environment variables. Its running containers are stopped and removed on the app server (queued agent action). Fails with 409 deploy_in_progress while a deploy is executing; retry once it finishes. This action cannot be undone.
Inputs: app_id (required).
deployado_delete_cron_jobCDestructive
Delete a cron job.
Inputs: app_id (required), cron_id (required).
deployado_delete_databaseADestructive
Permanently delete a managed PostgreSQL database. This will drop the database and remove all data. This action cannot be undone.
Inputs: database_id (required).
deployado_delete_envCDestructive
Delete a single environment variable from an app.
Inputs: key (required), app_id (required).
deployado_delete_projectADestructive
Delete a project and all its associated apps, stopping and removing each app's containers. Fails with 409 deploy_in_progress while one of its apps is being deployed. This action cannot be undone.
Inputs: project_id (required).
deployado_deployA
Trigger a new deployment for an app. Returns immediately with a release_id while the build runs in the background.
The deployment process: source code is cloned → Docker image is built → image is pushed → container is deployed.
After triggering:
Use deployado_get_release with the returned release_id to check build status (queued → pending → building → ready or failed).
If the build fails, use deployado_get_build_logs with the release_id to see the Docker build output.
commit_sha is optional — if omitted, the latest commit from the configured branch is used.
For runtime container logs after deployment, use deployado_get_logs.
Inputs: app_id (required), branch, commit_sha.
deployado_deploy_blueprintBDestructive
Deploy an entire application stack from a blueprint. Can use inline YAML content or a GitHub repository URL.
Inputs: branch, content, server_id, project_id, +1 more.
deployado_disconnect_databaseBDestructive
Disconnect an app from a database, removing the injected environment variable.
Inputs: database_id (required), connection_id (required).
deployado_doctorARead-onlyIdempotent
Run a fixed diagnostic checklist against one app. Returns structured results plus a roll-up: deployment status, latest build, target server health, instance count, HTTP probe of the primary domain, env vars, placement. Use this as the first stop when triaging 'app X is acting weird'. Mirrors the deployado doctor CLI command.
Inputs: app_id (required), deep.
deployado_execADestructive
Execute a command inside an app's running container. Timeout is 60 seconds. Returns exit code, stdout, and stderr.
Inputs: app_id (required), command (required), working_dir.
deployado_get_appCRead-onlyIdempotent
Get detailed information about a specific app.
Inputs: app_id (required).
deployado_get_backup_targetBRead-onlyIdempotent
Get a backup target's details and its recent backup runs.
Inputs: target_id (required).
deployado_get_build_logsARead-onlyIdempotent
Fetch build logs for a specific release. Use this to diagnose why a build failed.
Returns the Docker build output, including Dockerfile parsing errors, dependency installation logs, and compilation output. If the build is still in progress, returns partial logs collected so far.
IMPORTANT: This returns BUILD logs (from the Docker build process), not runtime container logs. For runtime logs of a running app, use deployado_get_logs instead.
Inputs: app_id (required), release_id (required).
deployado_get_databaseARead-onlyIdempotent
Get detailed information about a database, including connection URL and credentials.
Inputs: database_id (required).
deployado_get_deploymentBRead-onlyIdempotent
Get detailed information about a specific deployment, including phases and error details.
Inputs: app_id (required), deployment_id (required).
deployado_get_logsARead-onlyIdempotent
Fetch recent runtime logs from a running app's container. NOTE: These are runtime/application logs, NOT build logs. To see build output (e.g. why a deploy failed), use deployado_get_build_logs instead.
Inputs: app_id (required), lines, timestamps.
deployado_get_projectARead-onlyIdempotent
Get detailed information about a specific project.
Inputs: project_id (required).
deployado_get_releaseARead-onlyIdempotent
Get detailed information about a specific release, including build status, commit info, and error details. Use this to check if a build succeeded or failed after triggering a deploy.
Inputs: app_id (required), release_id (required).
deployado_get_serverARead-onlyIdempotent
Get detailed information about a specific server, including agent version, OS, architecture, and Docker version.
Inputs: server_id (required).
deployado_get_serviceCRead-onlyIdempotent
Get detailed information about a specific installed service.
Inputs: service_id (required).
deployado_install_serviceC
Install a new service from a marketplace template.
Inputs: name (required), template_id (required), config, memory_mb.
deployado_list_appsBRead-onlyIdempotent
List all apps in your Deployado account. Optionally filter by project ID.
Inputs: project_id.
deployado_list_backup_targetsARead-onlyIdempotent
List all database backup targets configured for your account.
Inputs: no named parameters.
deployado_list_cron_jobsARead-onlyIdempotent
List all cron jobs for an app.
Inputs: app_id (required).
deployado_list_databasesARead-onlyIdempotent
List all managed PostgreSQL databases. Optionally filter by project or status.
Inputs: status, project_id.
deployado_list_deploymentsARead-onlyIdempotent
List recent deployments for an app, showing status, version, and timing.
Inputs: app_id (required), limit.
deployado_list_domainsBRead-onlyIdempotent
List all custom domains for an app, including the auto-generated subdomain.
Inputs: app_id (required).
deployado_list_envARead-onlyIdempotent
List all environment variables for an app. Values of secret variables may be masked.
Inputs: app_id (required).
deployado_list_projectsBRead-onlyIdempotent
List all projects in your Deployado account.
Inputs: no named parameters.
deployado_list_releasesARead-onlyIdempotent
List available releases for an app, showing version history and build status. Each release has a status: queued, pending, building, ready (success), or failed. Use deployado_get_build_logs with a release_id to see build output.
Inputs: app_id (required), limit.
deployado_list_serversARead-onlyIdempotent
List all servers with their status and resource metrics (CPU, memory, disk).
Inputs: no named parameters.
deployado_list_servicesBRead-onlyIdempotent
List all installed services for your account.
Inputs: status.
deployado_list_service_templatesBRead-onlyIdempotent
Browse available service templates from the Deployado marketplace (databases, caches, monitoring tools, etc.).
Inputs: category.
deployado_release_logsARead-onlyIdempotent
Fetch the docker build transcript for a release. Works for both in-progress and finished builds. Returns the full logs plus status/timing metadata. Use this when investigating a build failure — the release ID comes from deployado deploy output or the releases field of an app's deployment.
Inputs: release_id (required), tail.
deployado_remove_domainCDestructive
Remove a custom domain from an app.
Inputs: app_id (required), domain_id (required).
deployado_restart_serviceC
Restart a service.
Inputs: service_id (required).
deployado_restore_backupADestructive
Restore a database from a specific backup run. This will overwrite the target database.
Inputs: run_id (required), target_id (required), drop_first, destination_target_id.
deployado_rollbackCDestructive
Rollback an app to a previous release version.
Inputs: app_id (required), version, release_id.
deployado_run_backupC
Trigger an immediate backup for a target.
Inputs: target_id (required).
deployado_run_cron_jobB
Manually trigger a cron job to run immediately.
Inputs: app_id (required), cron_id (required).
deployado_set_envADestructive
Set or update environment variables for an app. Merges with existing variables. A redeploy may be triggered automatically.
Inputs: env (required), app_id (required).
deployado_set_primary_domainBIdempotent
Set a domain as the primary domain for an app. The primary domain is used for redirects.
Inputs: app_id (required), domain_id (required).
deployado_start_serviceAIdempotent
Start a stopped service.
Inputs: service_id (required).
deployado_stop_serviceCDestructive
Stop a running service.
Inputs: service_id (required).
deployado_update_appCDestructive
Update an existing app's configuration.
Inputs: app_id (required), name, port, build_context, +7 more.
deployado_update_cron_jobCDestructive
Update an existing cron job.
Inputs: app_id (required), cron_id (required), name, status, +4 more.
deployado_update_projectCDestructive
Update a project's name, description, or other settings.
Inputs: project_id (required), name, description, default_branch, +1 more.
deployado_validate_blueprintARead-onlyIdempotent
Validate a Deployado blueprint YAML without deploying it. Returns validation results and a preview of what would be created.
Inputs: content (required).
deployado_verify_domainsAIdempotent
Verify DNS configuration for all domains of an app. Returns per-domain verification status.
Inputs: app_id (required).
deployado_whoamiARead-onlyIdempotent
Show current account, user, and API token information. Useful to verify authentication is working.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Related MCP Connectors
Deploy apps from GitHub, read build/runtime logs, and manage your app's users from your AI agent.
Deploy and run your apps by asking your AI: services, Postgres, logs, traces, rollbacks, costs.
Deploy and manage your apps, databases, storage, and scheduled jobs from your AI agent
Deploy your project to a live HTTPS URL from your AI tool; read logs, set variables, resize apps.
Related MCP Servers
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- 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

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