Connect EQVPS to your MCP client (Claude Desktop, Cursor, Cline)

EQVPS exposes a remote Model Context Protocol (MCP) server, so an AI agent inside your MCP client can rent and operate a real VPS without you clicking through a dashboard. This guide shows how to wire it into Claude Desktop, Cursor, or Cline in a few minutes.

What you're connecting to

Catalog tools (like list_plans) are public. Everything that touches an account or a server needs a Bearer token.

Step 1 — Get a Bearer token

You don't need a password or a sign-up form. Connect the server (you can connect with no auth header first), then have your agent call the register_account tool with a name and email:

// tool call: register_account
{ "first_name": "Ada", "last_name": "Agent", "email": "[email protected]" }
// → { "token": "<your Bearer token>", "token_type": "Bearer", ... }

Store the returned token. It's a long-lived bearer credential — send it as Authorization: Bearer <token> on every authenticated call.

Step 2 — Configure your client

Claude Desktop

Claude Pro, Team, and Enterprise can add a remote MCP server directly under Settings → Connectors (paste the endpoint URL and the Authorization: Bearer header). For Claude Desktop on the classic stdio setup, bridge the remote endpoint with mcp-remote — the universal path for any stdio client. Edit claude_desktop_config.json:

{
  "mcpServers": {
    "eqvps": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://mcp.eqvps.com/mcp",
        "--header", "Authorization: Bearer YOUR_TOKEN"
      ]
    }
  }
}

Tip: to mint the token in the first place, connect once without the --header line, ask Claude to call register_account, then paste the token in and restart.

Cursor

Cursor supports remote MCP servers directly. In .cursor/mcp.json (project) or your global Cursor MCP settings:

{
  "mcpServers": {
    "eqvps": {
      "url": "https://mcp.eqvps.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_TOKEN" }
    }
  }
}

Cline

In Cline's MCP settings, add a remote server with the URL https://mcp.eqvps.com/mcp and an Authorization: Bearer YOUR_TOKEN header. Cline speaks Streamable HTTP natively, so no bridge is needed.

Step 3 — Use it

Once connected, your agent can run the tools. A typical first session:

1. list_plans — see plans, specs, and which OS images each can boot (no auth).
2. register_account — get your token (no auth).
3. topup_balance — fund a prepaid balance with crypto (returns a checkout URL).
4. order_vps — order a plan with an os_id; add an ssh_key for key-based root.
5. get_vps_status — poll until the server is active; read SSH host/port.
6. power_vps, set_hostname, get_vps_metrics, reinstall_vps, cancel_service — operate it.

The full set is 16 tools — see the EQVPS MCP tools reference for every tool, its parameters, and examples.

Paying with crypto

EQVPS is crypto-native: you pay in USDC or USDT on Base, Ethereum, or Tron — no card required. The cleanest pattern for agents is a prepaid balance: call topup_balance once, pay the returned crypto checkout, then order_vps spends from the balance automatically — the agent never touches a wallet again. If you overpay (exchange withdrawal minimums are often higher than a small order), the surplus is credited to your balance, not lost.

Ready?

Point your MCP client at https://mcp.eqvps.com/mcp, call register_account, and your agent can stand up its own server in about a minute. See the tools reference next, or the Docs for the REST API.