What can you do with the Hetzner Cloud integration?

LiveContext exposes 19 operations on Hetzner Cloud, covering server, firewall, ssh key and volume. Common uses include Server provisioning, Capacity planning and Unresponsive server.

LiveContext

All integrations

Hetzner Cloud integration

Cloud infrastructure API for managing servers, networks, load balancers, and storage. Create and manage virtual servers, configure firewalls, handle floating IPs, and orchestrate cloud resources. Perfect for DevOps, infrastructure automation, and cloud-native applications.

19 toolsTokenAPI docs

Connect Hetzner Cloud How integrations work

Common Hetzner Cloud use cases

Server provisioning
Capacity planning
Unresponsive server
Infrastructure inventory
Access control
Cost saving
Troubleshooting
Backup management
Cleanup
Maintenance

What you can do with Hetzner Cloud

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Server, 9 operations

POSTcreate_server
Creates a new cloud server with specified configuration.
DELETEdelete_server
Permanently deletes a server.
GETget_server
Retrieves detailed information about a specific server.
GETlist_servers
Retrieves all cloud servers with optional filtering.
POSTpower_off_server
Forcefully powers off a server (hard shutdown).
POSTpower_on_server
Powers on a stopped server.
POSTreboot_server
Gracefully reboots a running server via ACPI signal.
POSTreset_server
Forcefully resets a server by cutting power and restarting.
POSTshutdown_server
Gracefully shuts down a server via ACPI signal.

Firewall, 2 operations

POSTcreate_firewall
Creates a new firewall with specified rules.
GETlist_firewalls
Retrieves all firewall configurations.

Ssh key, 2 operations

POSTcreate_ssh_key
Adds a new SSH public key for server access.
GETlist_ssh_keys
Retrieves all SSH keys for server access.

Volume, 2 operations

POSTcreate_volume
Creates a new block storage volume.
GETlist_volumes
Retrieves all block storage volumes.

Image, 1 operation

GETlist_images
Retrieves available OS images and snapshots.

Load balancer, 1 operation

GETlist_load_balancers
Retrieves all load balancers.

Network, 1 operation

GETlist_networks
Retrieves all private networks.

Server type, 1 operation

GETlist_server_types
Retrieves available server configurations and pricing.

Use Hetzner Cloud from Claude Code, Cursor or Codex

Connect Hetzner Cloud in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Hetzner Cloud operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Hetzner Cloud

Create your workspace
Sign up free. Nothing to install.
Connect Hetzner Cloud once
Add your Hetzner Cloud connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Hetzner Cloud integration FAQ

What can you do with the Hetzner Cloud integration?: LiveContext exposes 19 operations on Hetzner Cloud, covering server, firewall, ssh key and volume. Common uses include Server provisioning, Capacity planning and Unresponsive server.