DevPilot

DevPilot is an MCP server that automates VPS initialization and ongoing management via SSH-based workflows. It exposes a collection of tools to connect to a fresh VPS, initialize common services, configure Nginx with SSL, and set up GitHub Actions-based CI/CD deployments. Use the SSH Connect tool to establish a secure session, then run VPS Initialize to install and configure Node.js, PM2, Rust, Nginx, and Redis as needed. With Nginx Setup you can configure domain-based reverse proxy and SSL certificates, and GitHub CI/CD Setup will generate a deploy key, create a workflow, and guide you through adding secrets to your repository. The Execute Command tool lets you run arbitrary commands on the connected VPS for quick checks or custom tasks. These tools enable end-to-end automation of provisioning, deployment, and maintenance tasks for VPS-based applications.

Prerequisites:

• A fresh Ubuntu/Debian VPS with root or sudo access
• Node.js 18+ and npm
• Git installed on the VPS (for CI/CD workflows)

Setup steps:

1. Clone the MCP repository and install dependencies

   git clone <repository-url>
   cd mcp-vps-initialize
   npm install
   

2. Build the project (if applicable) and start the MCP server

   npm run build
   npm start
   

3. (Optional) Run in development mode during setup

   npm run dev
   

4. Verify the MCP server is running and accessible on the configured port (default 3000).

   curl http://localhost:3000/health
   

Tips and considerations:

• The MCP server assumes SSH access to a target VPS. Ensure the VPS allows SSH connections and that the user has appropriate privileges for software installation.
• When enabling SSL via Certbot in Nginx Setup, ensure your domain DNS points to the VPS. Open ports 80 and 443 in your firewall.
• For CI/CD workflows, securely store deploy keys and GitHub secrets as directed by the generated guidance. The workflow, deploy key, and secrets are designed to minimize exposure of sensitive data.
• The server can be configured via environment variables. Common options include LOG_LEVEL (e.g., debug, info, warn) and PORT for standalone deployments. Review logs in logs/ for troubleshooting.
• If you encounter SSH connection failures, verify network access, firewall rules, and that the SSH service is running on the VPS.