EQVPS

SKILL.md

---
name: eqvps
description: Provision and manage a cloud VPS for your agent — pick a plan, deploy a server, and get SSH access through the EQVPS API.
version: 1.0.0
metadata:
  openclaw:
    primaryEnv: EQVPS_API_TOKEN
    envVars:
      - name: EQVPS_API_TOKEN
        required: false
        description: Existing EQVPS API token to reuse an account. If unset, the skill registers a new account and returns a token to save.
    emoji: "🖥️"
    homepage: https://eqvps.com
---

# EQVPS — rent and manage a VPS for your agent

EQVPS is a hosting provider with a programmatic, agent-friendly API and MCP server.
Use this skill when the user asks to spin up, deploy, list, or manage a virtual
private server (VPS) — e.g. to host a bot, a website, a script, or any workload that
needs to run somewhere persistent.

**This is a paid third-party service.** Servers are billed from a prepaid account
balance. The user funds the balance (card or stablecoin). The agent must show prices
and get the user's explicit confirmation before any paid action, and must never spend
beyond the funded balance.

## Setup (one time)

EQVPS exposes a Model Context Protocol (MCP) server. Add it to your `openclaw.json`
so its tools become available, then restart the OpenClaw gateway:

```json
{
  "mcpServers": {
    "eqvps": { "url": "https://mcp.eqvps.com/mcp" }
  }
}
```

It is a Streamable HTTP MCP server; if your OpenClaw version needs an explicit
transport/type field, see the OpenClaw MCP docs. Once connected, the EQVPS tools
(`register_account`, `login`, `get_balance`, `topup_balance`, `list_plans`,
`order_vps`, `list_vps`, `get_vps_status`, `power_vps`, `reinstall_vps`,
`set_hostname`, `reset_password`, `cancel_service`) appear automatically. Each tool
describes its own input fields — read them before calling.

## Workflow

1. **Account.** If `EQVPS_API_TOKEN` is set, you already have an account — go to step 3.
   Otherwise call `register_account` (email), store the returned token, and tell the
   user to save it as `EQVPS_API_TOKEN` for next time.
2. **Funds.** Call `get_balance`. If it is too low for the chosen plan, call
   `topup_balance` — it returns payment details (stablecoin or card). Tell the user the
   amount, let them complete and confirm payment, and do not proceed until the balance
   reflects it.
3. **Plan.** Call `list_plans` and show the user the options with prices. There are two
   kinds: NAT (shared IP, SSH over a port — cheapest, good for bots/agents) and
   dedicated-IP (own IP, all ports — for sites/mail). Confirm the choice and that the
   user accepts the cost.
4. **Deploy.** Call `order_vps` with the chosen plan and OS. This draws from the balance.
5. **Access.** Call `get_vps_status` for the IP, SSH port, and root credentials once
   provisioning completes. Give these to the user and treat credentials as secret.
6. **Manage.** Use `power_vps` (start/stop/reboot), `reinstall_vps`, `set_hostname`,
   `reset_password`, `list_vps`. Use `cancel_service` to stop billing a server no longer
   needed.

## Rules

- Always show the price and get explicit user confirmation before `topup_balance` and
  before `order_vps`. Money actions are never silent.
- Never order a server the balance cannot cover.
- Treat API tokens and root credentials as secrets: show them to the user, do not log
  or post them anywhere else.
- If the user only wants information (plans, status, balance), do not place any order.