In the console, under Account → API Keys, create a key and allow the IP address of the machine your agent runs on. Keys only work from the addresses you choose, and you can limit a key to read-only.
Install the Hostereo MCP server with one command and add it to Claude Code, Cursor, Codex, Windsurf, Claude Desktop or any other MCP client. No SDK, no boilerplate.
"Create an Ubuntu 24.04 server in Tel Aviv on the Basic plan and give me its IP." The agent picks the plan, region and image from the live catalogue, creates the instance and reports back when it is running.
Requires Node.js 18 or newer. Replace hst_live_your_key with the key from the console.
npm install -g https://www.hostereo.com/downloads/hostereo-mcp-latest.tgz
claude mcp add hostereo -e HOSTEREO_API_KEY=hst_live_your_key -- hostereo-mcp
Then, inside Claude Code: "List my Hostereo instances" or "Create a WordPress server in Amsterdam".
Settings → MCP → Add new global MCP server, or edit ~/.cursor/mcp.json:
{
"mcpServers": {
"hostereo": {
"command": "hostereo-mcp",
"env": { "HOSTEREO_API_KEY": "hst_live_your_key" }
}
}
}
In ~/.codex/config.toml:
[mcp_servers.hostereo]
command = "hostereo-mcp"
env = { HOSTEREO_API_KEY = "hst_live_your_key" }
Every MCP client accepts the same definition in its MCP settings file (for Claude Desktop: claude_desktop_config.json):
{
"mcpServers": {
"hostereo": {
"command": "hostereo-mcp",
"env": { "HOSTEREO_API_KEY": "hst_live_your_key" }
}
}
}
- Browse the live catalogue: regions, plans, OS images, 1-click apps (WordPress, Supabase, OpenVPN and more)
- Create instances from an OS image or an app, prepaid or postpaid
- Start, stop, reboot, hard reboot, resize
- Read live status, connection details and the console URL
- Organise instances in projects and tags
- Follow every operation until it succeeds or fails
- Creates run as a dry run first: every check, nothing built or charged, until you confirm
- Every create, power action or resize needs an explicit confirmation from you
- Keys are bound to your IP addresses and can be scoped to read-only
- Deleting a server is deliberately not possible through the API: that stays in the console
- Open source, MIT licensed, 33 tools, no telemetry
The MCP server is a thin layer over our public REST API. Same key, same capabilities, from any language, CI pipeline or Terraform.
curl -s https://api-public.hostereo.com/api/v1/regions
curl -s -X POST https://api-public.hostereo.com/api/v1/instances \
-H "X-Api-Key: hst_live_your_key" -H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{"plan_id":"<plan uuid>","region":"tlv-dc-1","image_id":"<image uuid>","name":"build-1","dry_run":true}'
Interactive reference and OpenAPI 3.1 specification: https://api-public.hostereo.com/api/docs
No forms to study. One click opens Claude with a ready prompt: it reads our agent guide, walks you through the account and the API key, sets up the MCP server in your coding agent and creates your first server, dry run first.
Using another agent? Point it at https://www.hostereo.com/llms.txt: a plain-text guide with the signup URL, the API contract and the MCP install. Machine-readable manifest: /.well-known/hostereo-agent.json.
Sign up, create a key, paste one command. Your first servers are minutes away.
Create a free account