About hostkey-cloud
hostkey-cloud connects MCP clients to the Hostkey .com portal through InvAPI. Its typed tools cover server operations, DNS, S3, and billing, with safeguards for writes and long-running tasks.
Key features
- 01132 typed tools plus raw API calls
- 02Manage servers, power, and orders
- 03Handle DNS, network, snapshots, and S3
- 04Access billing and Remote Hands
- 05Require confirmation for write operations
- 06Poll long jobs with callback keys
Use cases
- 01Check server status and manage power
- 02Order or reinstall a server with safeguards
- 03Manage DNS records and S3 buckets
- 04Track deployment or reinstall tasks
MCP support
The MCP server exposes Hostkey .com InvAPI account operations to MCP clients. It runs locally over stdio or connects through the hosted endpoint; write calls require confirmation.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://mcp.hostkey.com/mcpclaude mcp add --transport http hostkey-cloud https://mcp.hostkey.com/mcp{"mcpServers":{"hostkey-cloud":{"type":"http","url":"https://mcp.hostkey.com/mcp"}}}Open in Cursor{"servers":{"hostkey-cloud":{"type":"http","url":"https://mcp.hostkey.com/mcp"}}}Open in VS Code{"mcpServers":{"hostkey-cloud":{"type":"http","url":"https://mcp.hostkey.com/mcp"}}}{"mcpServers":{"hostkey-cloud":{"serverUrl":"https://mcp.hostkey.com/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
https://mcp.hostkey.com/mcpAuth requiredTools
Details
From the project READMEHostkey MCP Server
MCP server for Hostkey (.com portal, InvAPI invapi.hostkey.com).
Runs locally over stdio — Cursor, VS Code, and other MCP clients.
Hosted remote: https://mcp.hostkey.com/mcp (cloud agents).
| Endpoint | https://invapi.hostkey.com (hardcoded) |
| Auth | HOSTKEY_API_KEY |
| Tools | 132 typed tools + call_api_raw |
Gives the model access to your Hostkey account: servers, catalog and ordering, power, OS reinstall, network, DNS, snapshots, IPMI/console, ISO, S3, Remote Hands, billing, and API keys.
1. Get an API key
InvAPI → API keys → create a key.
Prefer a dedicated key for MCP. Per-server keys limit access to one server.
DNS writes need the pdns/edit permission.
2. Install
Cursor
Click the button, replace YOUR_API_KEY with your InvAPI key, then confirm.
Or add to .cursor/mcp.json manually:
{
"mcpServers": {
"hostkey-mcp-server": {
"command": "npx",
"args": ["-y", "hostkey-mcp-server"],
"env": {
"HOSTKEY_API_KEY": "your-api-key"
}
}
}
}
Remote (cloud agents)
No local Node/npx. Point the client at the hosted endpoint and send your InvAPI key:
{
"mcpServers": {
"hostkey": {
"url": "https://mcp.hostkey.com/mcp",
"headers": {
"Authorization": "Bearer your-api-key"
}
}
}
}
VS Code
.vscode/mcp.json:
{
"servers": {
"hostkey-mcp-server": {
"command": "npx",
"args": ["-y", "hostkey-mcp-server"],
"env": {
"HOSTKEY_API_KEY": "your-api-key"
}
}
}
}
Optional: HOSTKEY_TOKEN_TTL, HOSTKEY_HTTP_TIMEOUT, HOSTKEY_ALLOW_DESTRUCTIVE
(see .env.example).
From source (Node.js ≥ 22.18): npm install && npm run build.
3. Confirming dangerous operations
Every write call needs confirm=true. Without it, nothing changes.
Also:
order_serverdefaults todry_run— a real order only after explicit consent;- OS reinstall, PXE, and service cancellation require
HOSTKEY_ALLOW_DESTRUCTIVE=1; - passwords and tokens are masked in responses.
Long jobs (deploy, reinstall) return a callback key — poll with check_task.
4. Tools
Groups (full list via tools/list):
| Group | Examples |
|---|---|
| Servers | get_servers, get_server, get_power_status |
| Catalog | list_presets, list_os, list_traffic_plans |
| Power & order | power_on, power_off, order_server, reinstall_server |
| PXE | create_reinstall_task → … → clear_pxe_config |
| Network / DNS | ports, PTR, zones and records |
| Snapshots, ISO, S3 | VM snapshots, images, buckets |
| Remote Hands | duty-shift tickets (request_rh_*, rhr_*) |
| Billing | invoices, payments, contacts |
| Misc | check_task, call_api_raw |
Prompts
| Prompt | Purpose |
|---|---|
order_server_prompt | guided server order |
reinstall_server_prompt | OS reinstall |
troubleshoot_server_prompt | diagnostics |
Or just ask: “list my servers” / “order a VPS in NL”.
Docs
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.