Install Lumic Control Center once, connect it to your coding agent through MCP, and open the UI whenever you want direct visibility and control.
ssh root@server 'curl -fsSL https://lumic.cc/install.sh | sh' Lumic Control Center
│
┌──────┼──────┐
│ │ │
CLI UI MCP
│ │ │
└──────┼──────┘
│
Linux VPSTurn a fresh Linux VPS into a Lumic node with one command. Lumic detects the host and establishes the daemon, CLI and management foundation.
ssh root@server 'curl -fsSL https://lumic.cc/install.sh | sh'Expose structured server capabilities to Codex, Claude or another MCP client instead of making unrestricted SSH the normal agent interface.
lumic mcp setupUse the clean Rust management interface when you want direct visibility and control over the same state and operations available through MCP and CLI.
lumic uiInspect this Lumic node and the current repository. Prepare the VPS as a production environment for this application. Detect the required runtime, system packages, extensions and backing services. Install only what is needed, configure the web server, database, cache, TLS, firewall, workers and scheduled jobs where applicable, and create a zero-downtime Git deployment from the repository. Use Lumic plans before material changes, keep the host secure, verify the deployment with health checks, and report exactly what was configured. Do not use unrestricted shell access when a Lumic capability exists.
Codex or Claude supplies the reasoning. Lumic supplies trustworthy host status, policy, plans, structured operations and auditability.
MCP documentation →api deployment completed
certificate renewed
postgres backup completed
PHP and required extensions, Composer, Nginx, PostgreSQL or MariaDB, Redis when needed, TLS, environment configuration, workers/Horizon, scheduler, Git deployment and zero-downtime releases.
Inspect the repository, install its Node/build requirements, handle static or server-rendered output, configure environment variables, Nginx, TLS, health checks and automatic Git deployments — a Render/Vercel-like workflow on infrastructure you own.
Packages, runtimes, extensions, users, processes, networking, firewall, storage, logs and diagnostics become structured Lumic operations rather than recurring SSH archaeology.
Git hosting, database management, Redis, certificates, backups, webhooks, notifications, event history, load tracing, managed services and multi-node infrastructure should increasingly feel like: “oh, Lumic supports that too.”
Early Lumic development ships a rolling nightly channel after CI gates pass. New capabilities, fixes and integration coverage arrive continuously while the stable channel remains conservative.