Back to Browse

Hostkey Cloud MCP Server

Developer ToolsModerate6.8MCP RegistryLocal
Free

Server data from the Official MCP Registry

MCP server for Hostkey .com (InvAPI): servers, power, order, DNS, S3, billing

About

MCP server for Hostkey .com (InvAPI): servers, power, order, DNS, S3, billing

Security Report

6.8
Moderate6.8Moderate Risk

This is a well-structured MCP server for the Hostkey cloud hosting platform with appropriate authentication, reasonable permission scoping, and good security practices for a developer tools category server. The codebase implements proper confirmation mechanisms for destructive operations, environment variable guards, and secret masking. Minor code quality observations exist but do not constitute security vulnerabilities. Supply chain analysis found 1 known vulnerability in dependencies (0 critical, 1 high severity). Package verification found 1 issue.

7 files analyzed · 6 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

InvAPI API key for the .com portal (invapi.hostkey.com); per-server keys supportedRequired

Environment variable: HOSTKEY_API_KEY

Session token TTL in seconds (default 3600)Optional

Environment variable: HOSTKEY_TOKEN_TTL

Set to 1 to allow destructive operations (OS reinstall, PXE cycle, service cancellation)Optional

Environment variable: HOSTKEY_ALLOW_DESTRUCTIVE

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-hostkey-cloud-mcp-server": {
      "env": {
        "HOSTKEY_API_KEY": "your-hostkey-api-key-here",
        "HOSTKEY_TOKEN_TTL": "your-hostkey-token-ttl-here",
        "HOSTKEY_ALLOW_DESTRUCTIVE": "your-hostkey-allow-destructive-here"
      },
      "args": [
        "-y",
        "hostkey-mcp-server"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

Hostkey 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).

Endpointhttps://invapi.hostkey.com (hardcoded)
AuthHOSTKEY_API_KEY
Tools132 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.

For the .ru portal use the separate package hostkey-mcp-server-ru.

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

Install in 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:

{
  "mcp.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 ≥ 20): npm install && npm run build.

3. Confirming dangerous operations

Every write call needs confirm=true. Without it, nothing changes.

Also:

  • order_server defaults to dry_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):

GroupExamples
Serversget_servers, get_server, get_power_status
Cataloglist_presets, list_os, list_traffic_plans
Power & orderpower_on, power_off, order_server, reinstall_server
PXEcreate_reinstall_task → … → clear_pxe_config
Network / DNSports, PTR, zones and records
Snapshots, ISO, S3VM snapshots, images, buckets
Remote Handsduty-shift tickets (request_rh_*, rhr_*)
Billinginvoices, payments, contacts
Misccheck_task, call_api_raw

Prompts

PromptPurpose
order_server_promptguided server order
reinstall_server_promptOS reinstall
troubleshoot_server_promptdiagnostics

Or just ask: “list my servers” / “order a VPS in NL”.

Reviews

No reviews yet

Be the first to review this server!