tugport
Related Servers
Alternatives to tugport
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables 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 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
- FlicenseNot gradedqualityBmaintenanceDeploy, manage, and scale applications directly from your AI assistant.7-
- 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
- AlicenseAqualityBmaintenanceDeploy internal apps built with AI behind your company login, each with its own database, file storage and secrets. Tools to deploy, read live logs, set who can open an app, assign roles and save secrets.12MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI clients and users to deploy static sites, Node.js services, and Python web applications without Docker, with tools for project management, deployment, rollback, and domain configuration.Apache 2.0
This server cannot be deployed
TDQS
Scored across 32 tools
Most tools target clearly distinct resources or lifecycle actions, and descriptions help separate similar areas like start/stop/restart/deploy. The main ambiguity is around backups: run_backup runs a job while backup_run retrieves a run, and metrics versus server_status overlap somewhat.
The set is mostly snake_case and readable, but conventions are mixed: many tools use verb_noun (list_services, create_project, cancel_deploy), while others are bare verbs (restart, deploy, stop) or noun phrases (metrics, audit_log, backup_run). The backup naming pair is especially inconsistent.
The server covers a broad PaaS/panel domain with projects, services, deploys, replicas, backups, servers, metrics and audit, so many tools are justified. However, 32 tools is heavy and could likely be consolidated or grouped more tightly.
Core workflows are well covered: project/service CRUD, deploys and rollback, env vars, domains, logs, metrics, replicas, backups and audit. Minor gaps remain, such as no project update/delete, no backup job creation/configuration, and no explicit domain listing.