Hetzner vs Terraform MCP Server
A side-by-side look at the Hetzner and Terraform MCP Server 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 Terraform MCP Server 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 Terraform MCP Server when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 59/100 · Good | 79/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | HETZNER_API_TOKENHETZNER_STORAGE_API_TOKEN | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 5 | 1,553 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 80 | Not listed |
| Full listing | View Hetzner | View Terraform MCP Server |
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
Terraform MCP Server tools
No tool names declared yet. Check the project README from the listing page.
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"
}
}
}
}
Terraform MCP Server
{
"mcpServers": {
"hashicorp-terraform-mcp-server": {
"url": "http://localhost:8080/mcp"
}
}
}
Frequently asked questions
Hetzner is categorized under Cloud Platforms and uses a local stdio subprocess. Terraform MCP Server belongs to Cloud Platforms and uses a remote HTTP/SSE transport. Pick Hetzner for cloud platforms work and Terraform MCP Server 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. Terraform MCP Server is listed as free. Auth: api key required. 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 hashicorp-terraform-mcp-server 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. Terraform MCP Server has 79/100 (Great) with 3 views, 0 installs and 1,553 GitHub stars.