ServerOS Panel Review: Open-Source Multi-VPS Panel With a Built-In MCP Server

Most self-hosted panels fall into two camps: PaaS-style deployers like Coolify and Dokploy that take over application hosting on the box, or Docker UIs like Portainer focused on inspecting containers per host. ServerOS (serveroshq/panel) aims at a different workflow: managing the Linux servers you already rent across providers from one central web dashboard. Connect an existing VPS with an enrollment command, and it joins your fleet for deploys, uptime checks, backups, and maintenance.

Built with Laravel/PHP and released under AGPL-3.0, ServerOS quickly passed 600 GitHub stars after launch. Its standout hook is a built-in Model Context Protocol (MCP) server that lets AI coding assistants query servers and run operations through the same permission-checked API the web UI uses.

How it works

The control panel itself runs as a centralized web app. Each managed Linux box runs serverosd, an open-source daemon (also AGPL-3.0) that opens an outbound connection back to the panel over port 8443. Because traffic initiates from the managed machine to the panel, nodes behind carrier-grade NAT or locked-down firewalls do not need extra inbound ports opened on the VPS firewall.

Once a machine enrolls, the panel gives you:

• Machines inventory showing CPU, memory, disk utilization, and pending OS package updates across hosts.
• Git deploys and staging clones supporting template or custom build paths with automatic domains and HTTPS certificates, plus one-click clones of a service to a separate test environment.
• Backups, monitors, and aggregated logs combining scheduled backups, HTTP uptime checks with alerts, per-service public status pages, and unified log views.
• Workflows chaining multi-step actions (such as deploy, health check, and promote) on a schedule, Git push, or manual trigger.
• Team controls with role assignments, two-factor authentication, and a central activity log.
• API and MCP server exposing fleet actions cleanly to scripts and external AI tools.

Rather than acting as a container-only dashboard like Portainer or replacing your host networking setup wholesale, ServerOS sits beside whatever workloads are already running on your Linux nodes.

Self-hosting the panel

Requirements are modest but opinionated: a Linux server with Docker, ports 80, 443, and 8443 open, and a domain with two A records: one for panel.example.com and a wildcard *.panel.example.com (workspaces live on subdomains).

The install is one script:

curl -fsSL https://raw.githubusercontent.com/serveroshq/panel/main/docker/self-hosted/install.sh \
  | sudo bash -s -- --domain=panel.example.com [email protected]

It installs Docker if needed, pulls the official image (ghcr.io/serveroshq/panel), and prints a setup code. Open https://panel.example.com, enter the code, and the installer walks you through email and your first account. If you lose the code: serveros-panel setup-code shows it again.

Connecting a server

In the panel UI, go to Machines > Connect machine to generate an enrollment command for each target VPS. Running it installs serverosd, which initiates an outbound connection back to port 8443 and reports CPU, memory, disk, and pending package updates within a few seconds.

That outbound daemon model is practical for mixed fleets. You avoid opening extra SSH or management ports on firewalls across providers, avoid managing SSH key rotation everywhere, and keep existing services untouched on boxes already doing real work.

Key features in detail

Deploys and staging clones center on Git repositories: attach a repo, pick a template or build configuration, and let ServerOS handle domain routing and TLS certificates. Cloning an existing service straight into a temporary test environment is especially handy before rolling changes to production.

Workflows act like cron combined with conditional deployment steps, letting you automate deploy, health-check, and promotion chains across nodes without standing up a separate CI runner.

Monitors and status pages handle straightforward HTTP uptime alerts alongside public per-service status pages. It will not replace Prometheus or Grafana (we covered broader panel tooling in best self-hosted panels), yet it answers whether a service is up without needing a second stack.

The MCP server wraps the panel’s API as Model Context Protocol tools, allowing an AI coding client to inspect nodes, check service state, kick off backups, or pull logs using the same role permissions as a human user. Keeping every agent command logged under the panel’s activity stream is far safer than handing an assistant a raw SSH key.

Editions and licensing: the honest read

Without an enterprise key, ghcr.io/serveroshq/panel runs the complete AGPL community edition with no artificial machine lockouts inside your self-hosted control plane. Buying a license activates panel-ee features aimed at teams (SSO, SCIM directory sync, custom roles, and custom domains), while hosted tiers on serveros.com start around £5/month for a single machine and £12/month for multi-machine workflows and status pages. Under AGPL-3.0, self-hosters running it internally pay nothing, while providers modifying the code to resell a SaaS panel must publish source changes.

How it compares

There is clear overlap with Coolify and Dokploy, though they solve slightly different problems. Coolify and Dokploy shine when deploying apps and compose stacks onto clean nodes; ServerOS leans toward operators managing five or ten existing VPSes across Hetzner, DigitalOcean, or AWS who want one place for OS health, workflows, status pages, and API/MCP operations. For pure app shipping, check our Coolify vs Dokploy vs Kamal comparison.

FAQ

Verdict

ServerOS is a compelling option to test in a lab if you already juggle multiple VPS instances across providers and want unified OS visibility, Git deploys, workflows, and audited MCP automation in one open-source package. Because the project is still brand new, keep it on replaceable or staging servers for a couple of release cycles before wiring it into your primary production fleet.

Related articles

• Best self-hosted panels (the wider field compared)
• Coolify vs Dokploy vs Kamal 2 (PaaS-style alternatives)
• Dokploy install guide (self-hosted PaaS setup)
• Portainer alternatives (for container management)
• Easypanel review (another modern panel option)