---
name: RepoCloud VPS Deployment
description: Deploy and manage Ubuntu VPS instances on RepoCloud
version: 1.0.0
trigger_keywords:
  - deploy
  - host
  - VPS
  - server
  - RepoCloud
  - Ubuntu
  - provision
  - SSH
mcp_server: https://mcp.repocloud.io/mcp
transport: streamable-http
auth: Bearer token (rcmcp_ prefix) in Authorization header
---

# RepoCloud VPS Deployment Skill

## What This Does

This skill lets you deploy a fresh Ubuntu 24.04 VPS instance on RepoCloud,
SSH into it as root, install and deploy any application, and manage the
server lifecycle (power on/off, reboot, resize, destroy).

## When to Use

- User asks you to deploy, host, or launch an application
- User needs a server or VPS for their project
- User wants to deploy something they built to a real server
- User mentions RepoCloud, VPS, or Ubuntu server

## Prerequisites

- A RepoCloud account with an API key (starts with `rcmcp_`)
- Account balance of more than $3 to deploy
- The MCP server configured in your client

## Workflow

### Step 1: Provision the VPS

Call `provision_ubuntu_vps` with:
- `project_name`: a short lowercase name for the project (hyphens OK)
- `flavor`: the server tier (default `s-2vcpu-2gb` with 2 vCPU, 2 GB RAM, 40 GB disk)

The response includes `instance_id`, `ipv4`, `root_password`, and SSH key details.

### Step 2: Wait for Active Status

Poll `get_instance_status` with the `instance_id` every 10-15 seconds until:
- `status` is `active` → server is ready, proceed to Step 3
- `status` is `failed` → terminal error, provision a new instance

Do NOT attempt to SSH until status is `active`.

### Step 3: SSH In and Deploy

Connect via SSH as root:
```
ssh root@<ipv4>
```

Use the `root_password` from the provisioning response, or the SSH key if
one was provided.

Install and deploy the application. Common patterns:
- Node.js app: `apt install nodejs npm && git clone ... && npm install && npm start`
- Python app: `apt install python3-pip && pip install ... && python app.py`
- Docker app: `apt install docker.io && docker run -d -p 80:8080 myapp`

### Step 4: Verify

Confirm the application is running by accessing `http://<ipv4>` or the
appropriate port.

### Step 5: Clean Up

When done, call `destroy_instance` with `confirm=True` to stop billing.

## Available Tiers

| Flavor          | vCPU | RAM    | Disk    | ~Monthly |
|-----------------|------|--------|---------|----------|
| s-1vcpu-2gb     | 1    | 2 GB   | 30 GB   | $6       |
| s-2vcpu-2gb     | 2    | 2 GB   | 40 GB   | $9       |
| s-2vcpu-4gb     | 2    | 4 GB   | 40 GB   | $12      |
| s-4vcpu-8gb     | 4    | 8 GB   | 80 GB   | $24      |
| s-8vcpu-16gb    | 8    | 16 GB  | 160 GB  | $49      |
| s-16vcpu-32gb   | 16   | 32 GB  | 320 GB  | $97      |

For heavy packages (Flowise, n8n, Supabase): use s-4vcpu-8gb or larger.
Install `build-essential` before npm packages with native addons.

## Important Notes

- The `s-1vcpu-1gb` tier is permanently unavailable for Ubuntu VPS
- Resize only scales UP — disk cannot be shrunk
- All billing is hourly from the moment of provisioning
- Destroy the instance when done to stop charges