API and MCP

Keys

Make a key on your profile page. You choose what it can do:

• Read only: see your account, servers, invoices and tickets.
• Read and server actions: also start, stop, reboot and reinstall your servers, and open and answer tickets.

The key is shown once, when you make it, and we email you whenever one is made. Keep it like a password: anyone who has it can do what it allows. Changing or resetting your password deletes every key. You can have 5 keys, and you can delete one at any time. Buying, renewing and paying are not part of the API.

Requests

Send JSON to https://10gbpsvps.com/api/v1, with your key in the Authorization header:

curl https://10gbpsvps.com/api/v1/servers \
  -H "Authorization: Bearer gbv_your_key"

curl -X POST https://10gbpsvps.com/api/v1/servers/12345678/reboot \
  -H "Authorization: Bearer gbv_your_key"

Answers are JSON. An error comes with a matching HTTP status and {"error": {"status": 404, "message": "No such server."}}. A key can make 120 requests a minute, and one server can take 30 actions an hour, counting those from the control panel.

Endpoints

Request	Key	What it does
GET /account	Any	Your email, name and balance.
GET /servers	Any	Your servers: state, IP addresses, plan, location, traffic, price and next payment date.
GET /servers/{id}	Any	One server, with the images it can be reinstalled with.
POST /servers/{id}/start	Actions	Start a stopped server.
POST /servers/{id}/stop	Actions	Stop a running server.
POST /servers/{id}/reboot	Actions	Reboot a running server.
POST /servers/{id}/reinstall	Actions	Erase the server and install an image. Body: {"image": "UBUNTU_24_04_64BIT", "confirm": "{id}"}.
GET /invoices	Any	Your invoices, newest first.
GET /tickets	Any	Your support tickets.
GET /tickets/{ref}	Any	One ticket with its messages.
POST /tickets	Actions	Open a ticket. Body: {"subject": "...", "message": "...", "topic": "Technical", "server": "{id}"}.
POST /tickets/{ref}/messages	Actions	Reply on a ticket. Body: {"message": "..."}.

Reinstalling erases everything on the server, so it runs only when confirm repeats the server id.

MCP for AI agents

The same tools are available over the Model Context Protocol, so an AI agent can list your servers, reboot one or open a ticket when you ask it to. The server is at https://10gbpsvps.com/mcp/ and uses the Streamable HTTP transport, with your key as a Bearer token.

In Claude Code:

claude mcp add --transport http 10gbpsvps https://10gbpsvps.com/mcp/ \
  --header "Authorization: Bearer gbv_your_key"

In Cursor and other clients that take a server address and headers:

{
  "mcpServers": {
    "10gbpsvps": {
      "type": "http",
      "url": "https://10gbpsvps.com/mcp/",
      "headers": { "Authorization": "Bearer gbv_your_key" }
    }
  }
}

Claude Desktop, claude.ai and ChatGPT can't send a key header yet. In Claude Desktop, use the mcp-remote bridge in claude_desktop_config.json. It needs Node.js:

{
  "mcpServers": {
    "10gbpsvps": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://10gbpsvps.com/mcp/", "--header", "Authorization:${AUTH}"],
      "env": { "AUTH": "Bearer gbv_your_key" }
    }
  }
}

Give an agent a read-only key unless you want it to act on your servers. A key with server actions lets it reboot and reinstall them.

For AI tools reading this site

A short summary of our plans, prices, locations and coins is at /llms.txt.