MCP Lightsail Deployment Server

What is MCP Lightsail Deployment Server?

The MCP Lightsail Deployment Server is a Model Context Protocol (MCP) server that automates deploying projects to AWS Lightsail instances, configures DNS via Cloudflare, and provides real-time progress tracking through Server-Sent Events (SSE). It is designed for developers and LLM-based clients who need to spin up and manage full‑stack deployments with minimal manual steps.

How to use MCP Lightsail Deployment Server?

Clone the repository, install dependencies (npm install), configure environment variables (AWS credentials, Cloudflare tokens, encryption key), build (npm run build), and start (npm start). The server exposes MCP tools (e.g., create_vm, redeploy_project, get_vm_status) and a SSE endpoint at /sse/:sessionId for real‑time deployment progress.

Key features of MCP Lightsail Deployment Server

• Automated AWS Lightsail instance creation with custom configurations
• Direct GitHub repository cloning and deployment
• Automatic Cloudflare DNS record creation and management
• Redeployment with a single command to pull latest code
• Real-time deployment progress via Server-Sent Events (SSE)
• Encrypted storage of sensitive credentials (AWS keys, SSH keys, GitHub tokens)

Use cases of MCP Lightsail Deployment Server

• Deploy a web application from a GitHub repo to a Lightsail VM with a custom domain
• Quickly spin up staging environments for testing and QA
• Redeploy an existing project after code changes without manual SSH steps
• Automate full‑stack deployments (Docker Compose + Caddy reverse proxy + SSL)

FAQ from MCP Lightsail Deployment Server

What does the server do?

It creates an AWS Lightsail instance, connects via SSH, installs Docker and Caddy, clones a GitHub repository, runs docker compose up -d, configures Cloudflare DNS, and returns the access URL — all through MCP tools.

What dependencies are required?

Node.js, npm, a GitHub Personal Access Token, AWS credentials (Access Key, Secret Key, SSH key), and Cloudflare API token with DNS edit permissions. The server handles the rest (Docker, Caddy installation) automatically.

How is real-time progress tracked?

After starting a deployment, the server returns a sessionId. Connect to GET /sse/:sessionId to receive Server‑Sent Events with types progress, log, error, complete, and status.

Where are credentials stored and are they safe?

Sensitive credentials (AWS keys, SSH keys, GitHub tokens) are encrypted at rest using the ENCRYPTION_KEY environment variable. Default configurations may also be stored in the .env file.

What transports or authentication are supported?

The server exposes HTTP endpoints (POST /mcp, GET /mcp, DELETE /mcp) for MCP protocol communication. It does not specify built‑in authentication; the README advises implementing proper access controls for the MCP server.