tugport
Manage a Tugport deployment end-to-end via MCP/API, from projects and services to deployments, domains, infrastructure, backups, and audit, subject to your grants.
Projects: list/get/create projects and inspect their services and shared variable names.
Services: create apps (Git/image/Dockerfile), databases (Postgres/MySQL/MariaDB/Mongo/Redis), or Compose stacks; get/update/delete/list services.
Deployments: deploy with wait/log/cache options, list/get/cancel deploys, roll back, restart, stop, or start services.
Runtime access: search logs, exec shell commands in running containers, and list/set/delete env vars (secret values only with
secrets:read).Domains: add/remove HTTPS domains, including wildcards and path-prefix routing across services/projects.
Infrastructure: list servers, get server status, query host/GPU/service metrics, and manage database read replicas.
Backups: list backup jobs, run backups now, and inspect backup/restore runs and logs.
Governance: query the audit log; destructive and secret-reading actions are gated by grants.
Runs alongside Docker to deploy apps and Compose stacks as containers, build with Dockerfiles, and manage the container runtime for services.
Deploys apps on push from Forgejo repositories using deploy keys, with health-checked releases and rollbacks.
Deploys from any Git server that supports deploy keys, triggering builds on push.
Deploys apps on push from Gitea repositories using deploy keys, with health-checked releases and rollbacks.
Deploys apps on push from GitHub repositories using deploy keys, with health-checked releases and rollbacks.
Deploys apps on push from GitLab repositories using deploy keys, with health-checked releases and rollbacks.
Creates and manages cloud servers at Hetzner, including regions, autoscaling, and scale-to-zero.
Provisions and manages MariaDB databases with domains, HTTPS, environment variables, volumes, limits, and backups.
Provisions and manages MongoDB databases with domains, HTTPS, environment variables, volumes, limits, and backups.
Provisions and manages MySQL databases with domains, HTTPS, environment variables, volumes, limits, and backups.
Provisions and manages Redis instances with domains, HTTPS, environment variables, volumes, limits, and backups.
Sends server and service alerts and notifications to Telegram.
Joins additional servers and regions into an encrypted WireGuard mesh for private networking.
Tugport is a self-hosted alternative to Heroku and Vercel for Docker apps, and an alternative to Coolify, Dokploy and Easypanel: you push code, and it builds and runs your apps on servers you own, with HTTPS, databases and backups. It is a single Rust binary that runs next to Docker. Install it on a Linux server with systemd (x86_64 or arm64):
curl -fsSL https://tugport.com/install | shThe installer sets up Docker if it is missing, starts Tugport as a system service and prints a one-time link for creating the owner account. Tugport is young (0.1.x), so expect rough edges.
What it does
Deploys on push from GitHub, Forgejo, Gitea, GitLab or any Git server with a deploy key, built with your Dockerfile, Railpack, Nixpacks or buildpacks. A new version gets traffic only after its health check passes, and rolling back takes one click.
Apps, Compose stacks and databases (Postgres, MySQL, MariaDB, MongoDB, Redis) with domains, automatic HTTPS, environment, volumes and limits. Certificates are proven over port 80 or, with a Cloudflare token, over DNS (wildcards included), and one domain can send different paths to services in different projects.
Logs and charts for every server and service, with alerts to Telegram, email or a webhook.
AI agents as users: an agent gets a scoped API key in one step, works through the API, the CLI or the MCP endpoint with the same permissions, and every action lands in the audit log.
Secrets that stay secret: encrypted at rest, delivered only to the containers that use them, and masked everywhere else.
More servers and regions joined by an encrypted WireGuard mesh, with cloud servers created at Hetzner or AWS, autoscaling, scale to zero and database replicas.
Backups of databases and volumes to S3-compatible storage or a disk, with test restores.
Automatic updates of Tugport itself without dropping traffic, on by default and off with one setting.
Moving from Easypanel or Coolify in one command while the apps keep running, with a rollback.
There is deliberately no app store, no one-click templates, no teams or organizations and no telemetry.
Related MCP server: DPLoy
How it compares
Coolify, Dokploy, Easypanel and CapRover do the same basic job as Tugport: they run your apps in Docker on your own servers behind HTTPS and give you a web panel. Tugport is the one that moves a running Easypanel or Coolify server over in one command and can roll that move back. It also documents autoscaling and scale to zero, joins servers through its own encrypted WireGuard network instead of Docker Swarm, and treats AI agents as users with their own roles, grants and audit trail. The panel, proxy, metrics and logs are one Rust program rather than a stack of services.
The alternatives are the better pick in plenty of cases. Coolify has hundreds of one-click templates, preview deployments and by far the largest community, and its self-hosted version is free with every feature. Dokploy has preview deployments on GitHub and a hosted plan if you would rather not run the panel yourself. CapRover and Dokku are small and have been around for years, and Kamal suits people who prefer to deploy over SSH from their own machine or CI with no panel at all. Tugport is young (0.1.x) and has a much smaller community, with no app store, templates, teams or preview deployments. Next to Heroku or Vercel, you run and pay for the servers yourself, and your apps run as long-lived containers, so there are no serverless functions or global edge network.
The full comparison has a feature table, prices and sources for every claim.
FAQ
Which should I use for a few apps on a Hetzner server?
Coolify, Dokploy, Easypanel and Tugport all install on a plain Linux VPS such as a Hetzner Cloud server. Easypanel is free for 3 projects and paid per server after that, while the other three are free to self-host. If you want one-click templates for popular apps, Coolify is the easiest start. If you want zero-downtime deploys, scheduled backups with test restores and room to grow, Tugport can later create more Hetzner servers through your API token and spread replicas across them. The Uptime Kuma guide walks through a Tugport install on a Hetzner VPS step by step.
How do I move my apps off Easypanel?
Install Tugport on the same server, which offers the move when it finds Easypanel, or run tugport migrate easypanel --dry-run to see the whole plan without changing anything. tugport migrate easypanel then moves projects, services, domains, certificates, environment, volumes and deploy webhooks while the apps keep running. Volumes stay where they are, certificates are imported rather than re-issued, and each database is down for a few seconds while it switches over. If anything goes wrong, tugport migrate rollback brings Easypanel back. Coolify works the same way with tugport migrate coolify. Some things, such as backup schedules, users and notification channels, are not moved; the migration guide lists them.
Does it work with AI coding agents?
Yes, and that is one of the reasons it exists. The owner creates an agent user in one step and gets a key for it, along with ready-made snippets for Claude Code, Codex, the CLI and curl. The agent gets a role on just the projects it needs, and it can't delete anything or read secret values unless you give it those separate grants; keys can also expire and be limited to certain IP ranges. Agents work through the REST API, the tugport CLI or the MCP endpoint (/mcp over HTTP, or tugport mcp for clients that start a command), and every action lands in the audit log with the key behind it. agents.md is a step-by-step guide an agent can follow to move a whole server to Tugport.
Security notes
Containers cannot reach the panel through the addresses configured on their own server, the server mesh or Tugport's internal endpoints. An address that lives on a NAT gateway instead, such as an EC2 Elastic IP or a home router's port forward, sends their traffic out and back in like any outside client's, so on such servers close the panel's port (8484) in the cloud firewall and use the panel through its domain.
Privileged mode, the Docker socket, host networking, bind mounts and extra capabilities stay off unless an admin with the destroy grant turns them on.
The master key is sealed to the server's TPM when it has one, otherwise kept in a root-only key file. Keep the recovery key the installer prints.
Documentation
API reference, including the MCP endpoint, at https://tugport.com/docs/api/
Moving from Easypanel or Coolify, at https://tugport.com/docs/migration/
Tugport compared with Coolify, Dokploy, Easypanel and CapRover, at https://tugport.com/docs/compare/
Deploy Uptime Kuma on a Hetzner VPS with Tugport, tested step by step, at https://tugport.com/docs/uptime-kuma/
Moving a server to Tugport, for AI agents, served at https://tugport.com/agents.md
Repository
Path | Contents |
| The binary: panel API, proxy, deploy engine, builders, node agent, CLI and MCP endpoint |
| The panel's web UI (Preact and Tailwind), embedded into release builds |
| API reference and migration guide |
| Docker-in-Docker boxes for building and testing on Linux ( |
| tugport.com, deployed to GitHub Pages on every push to |
The share image website/og.png is rendered from website/og.html with headless Chrome:
cd website && "/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" --headless=new --hide-scrollbars \
--window-size=1200,630 --virtual-time-budget=10000 --screenshot="$PWD/og.png" "file://$PWD/og.html"Each docs page has its own card in website/og/<slug>.png; after adding or renaming a guide in docs/guides.mjs, run node docs/og.mjs.
License
MIT
Available Tools
32 toolsadd_domainA
Serve a service on a domain with automatic HTTPS. The host may be a wildcard (*.example.com); several services, even in other projects, can share a host on different path prefixes, and the longest prefix wins.
Inputs: host (required), port (required), service (required), path, +2 more.
add_replicaA
Add a read replica to a database, on a given server or region (placement {node, region, labels}). MongoDB and MariaDB primaries restart once the first time.
Inputs: service (required), placement.
audit_logC
Who did what, newest first.
Inputs: actor, limit, project, service.
backup_runB
A backup or restore run: its status, progress while it runs, and its log.
Inputs: run_id (required).
cancel_deployB
Cancel a running or queued deploy.
Inputs: deploy_id (required).
create_projectC
Create a project.
Inputs: name (required), description.
create_serviceB
Create a service in a project. kind is app, database or compose. For apps pass spec.source ({type: git, repo, branch} | {type: image, image} | {type: dockerfile, content}); for databases pass database: {engine: postgres|mysql|mariadb|mongo|redis}.
Inputs: name (required), project (required), env, kind, +2 more.
delete_serviceA
Delete a service (needs the destroy grant). volumes=true also deletes its data.
Inputs: service (required), volumes.
deployA
Deploy a service and wait for the result (set wait=false to return immediately). Returns the deploy and the end of its log.
Inputs: service (required), ref, wait, no_cache.
execB
Run a shell command inside a service's running container (with its env) and return the output.
Inputs: command (required), service (required), timeout_s.
get_deployC
A deploy with its full log.
Inputs: deploy_id (required).
get_logsB
Search a service's logs. q is a case-insensitive substring; since/until are epoch milliseconds.
Inputs: service (required), q, limit, since, +2 more.
get_projectC
A project's services with live status, and its shared variable names.
Inputs: project (required).
get_serviceC
A service's spec, live status, replicas, domains, env var names and last deploy.
Inputs: service (required).
list_backupsC
Backup jobs with their last run. A volume job's volume is a named volume, or a folder of the server (a path) the service mounts.
Inputs: no named parameters.
list_deploysC
Recent deploys of a service.
Inputs: service (required).
list_envC
A service's env var names (values only if you hold secrets:read).
Inputs: service (required).
list_projectsA
List projects you can see, with your role in each.
Inputs: no named parameters.
list_replicasC
A database's read replicas and whether they follow it.
Inputs: service (required).
list_serversC
The servers in this setup (the panel's own is id local) with status, versions and size.
Inputs: no named parameters.
list_servicesB
Every service you can see across projects, with its state.
Inputs: no named parameters.
metricsA
Time series for a server (scope=host), a GPU (gpu:0) or a service (service:, added up over every server). range is 1h, 6h, 24h, 7d or 30d.
Inputs: node, names, range, scope.
promote_replicaA
Make a replica a primary when its primary is lost (admin). The old primary's URL variable then points at it.
Inputs: service (required).
remove_domainC
Remove a domain by id.
Inputs: domain_id (required).
restartC
Restart a service's containers.
Inputs: service (required).
rollbackC
Roll back to the previous version (or a given deploy_id).
Inputs: service (required), deploy_id.
run_backupC
Run a backup job now.
Inputs: job_id (required).
server_statusA
A server's current CPU, memory, disks, network, GPUs and per-service usage (default: the panel's own).
Inputs: node.
set_envB
Set or delete env vars: vars is {NAME: "value" or null}. Redeploy to apply.
Inputs: vars (required), service (required).
startB
Start a stopped service.
Inputs: service (required).
stopC
Stop a service.
Inputs: service (required).
update_serviceA
Change a service's settings with a JSON merge patch of its spec. Redeploy to apply.
Inputs: spec (required), service (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 32 tools
Most tools map cleanly to a resource+action (list_projects vs get_project, add_replica vs promote_replica, deploy vs list_deploys). The main confusion risks are the near-identical pair run_backup (trigger a job now) versus backup_run (fetch a run's status/log), and the metric/snapshot trio list_servers/server_status/metrics, which requires reading descriptions to separate. Overall mostly distinct with one or two confusable pairs.
A verb_noun pattern dominates (list_projects, create_service, cancel_deploy, get_logs), but it is broken by bare verbs (deploy, restart, stop, start, exec, rollback), noun-only tools (metrics, server_status, audit_log), and the reversed order in backup_run next to run_backup. Still readable, but no single predictable convention lets an agent infer names.
32 tools is heavy and beyond the comfortable range, though the surface spans many genuinely different domains (projects, services, deploys, env, domains, replicas, backups, servers, metrics, audit). Some consolidation is possible — start/stop/restart overlap as a single lifecycle concern, and run_backup/backup_run could be merged — but each domain carries roughly three tools, so it is large rather than bloated.
Core workflows are covered end to end: service CRUD, deploy lifecycle including cancel/rollback, env, domains, logs, exec, and backups. Notable gaps cause dead ends: no way to create or edit a backup job (only list/run), no remove/demote replica despite add/promote, no delete or update project, and no member/role management even though roles appear in list_projects and grant checks gate deletes.
Maintenance
Related MCP Connectors
Manage your own cloud with AI: deploy apps, push and ship custom Docker images, manage resources via your AI agent.
Deploy and run apps in your own AWS, Google Cloud, Azure or DigitalOcean account from any AI agent.
Let your AI agent deploy apps to your own server: AWS EC2 in your account or any SSH server.
Deploy sites and apps from your AI coding agent: domains, DNS, logs, env, versions and rollback.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceDeploy, manage, and scale applications directly from your AI assistant.8-
- AlicenseAqualityCmaintenanceEnables AI agents to deploy applications and manage servers over SSH using natural language commands, with built-in tools for Python bots, Docker Compose, and SSL setup.6MIT
- 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 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