Hetzner vs Hostinger API MCP
A side-by-side look at the Hetzner and Hostinger API MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Hetzner for cloud platforms work as a local process; choose Hostinger API MCP for cloud platforms over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Hetzner when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
HETZNER_API_TOKEN, HETZNER_STORAGE_API_TOKEN. - You want tools like
hetzner_list_servers, hetzner_get_server, hetzner_create_server.
Choose Hostinger API MCP when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
HOSTINGER_API_TOKEN, API_TOKEN, OAUTH_ISSUER, DEBUG. - You want tools like
search, execute, multi-execute.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 59/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | HETZNER_API_TOKENHETZNER_STORAGE_API_TOKEN | HOSTINGER_API_TOKENAPI_TOKENOAUTH_ISSUERDEBUG |
| Verified owner | Community listing | Community listing |
| GitHub stars | 5 | 164 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 80 | 3 |
| Full listing | View Hetzner | View Hostinger API MCP |
Tools & capabilities
Hetzner tools 80
hetzner_list_servershetzner_get_serverhetzner_create_serverhetzner_update_serverhetzner_delete_serverhetzner_power_onhetzner_power_offhetzner_reboothetzner_resethetzner_shutdownhetzner_rebuild_serverhetzner_resize_server- +68 more on the listing page
Hostinger API MCP tools 3
searchfind operations by keyword; returns each match with its `inputSchema`.executerun one operation: `{ "operation": "<name>", "params": { ... } }`.multi-executerun up to 20 operations in order, stopping at the first failure. A params value that is exactly `"$steps.<i>.<path>"` is replaced by that value from an earlier step's result.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Hetzner
{
"mcpServers": {
"hetzner": {
"command": "npx",
"args": [
"-y",
"@lazyants/hetzner-mcp-server"
],
"env": {
"HETZNER_API_TOKEN": "YOUR_HETZNER_API_TOKEN_HERE",
"HETZNER_STORAGE_API_TOKEN": "YOUR_HETZNER_STORAGE_API_TOKEN_HERE"
}
}
}
}
Hostinger API MCP
{
"mcpServers": {
"hostinger-api-mcp": {
"url": "https://mcp.hostinger.com"
}
}
}
Frequently asked questions
Hetzner is categorized under Cloud Platforms and uses a local stdio subprocess. Hostinger API MCP belongs to Cloud Platforms and uses a remote HTTP/SSE transport. Pick Hetzner for cloud platforms work and Hostinger API MCP for cloud platforms.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Hetzner has no declared pricing — check the project's own site. Hostinger API MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add hetzner and hostinger-api-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Hetzner has a quality signal of 59/100 (Good) with 0 views, 0 installs and 5 GitHub stars. Hostinger API MCP has 57/100 (Good) with 1 views, 0 installs and 164 GitHub stars.