Skip to main content
Glama

Related Servers

Alternatives to tugport

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      6
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to deploy and operate self-hosted applications on Linux servers and homelabs through Docker Compose, including zero-config buildpack builds, encrypted secret storage, one-second PostgreSQL/Redis provisioning, and one-call exposure via Cloudflare Tunnel or Tailscale. It also provides container lifecycle and log management plus an optional lightweight web dashboard, all without a persistent daemon.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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
    • A
      license
      A
      quality
      C
      maintenance
      Deploy 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.
      12
      MIT

    TDQS

    C2.9/5.0

    Scored across 32 tools

    Disambiguation4/5

    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.

    Naming Consistency3/5

    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.

    Tool Count3/5

    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.

    Completeness3/5

    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

    ActivityMaintained
    ResponsivenessNo recent community issues