Hetzner Cloud MCP Server

A secure, local MCP server that gives your LLM access to your Hetzner Cloud infrastructure. Your API token stays on your machine and is never sent to any LLM provider.

Features

• Server monitoring — list servers, check status, view CPU/disk/network metrics

• Firewall inspection — view firewall rules and which servers they're applied to

• Network overview — private networks, subnets, and routes

• Snapshot & backup management — list and create snapshots

• Health check — one-command overview with warnings for missing firewalls, stopped servers, etc.

Related MCP server: mcp-hetzner

Quick Start

1. Clone and install

git clone https://github.com/ivarwerner/hetzner-mcp.git
cd hetzner-mcp
chmod +x install.sh
./install.sh

2. Get a Hetzner API token

Go to Hetzner Cloud Console → Security → API Tokens → Generate API Token.

Use Read permissions for a read-only setup, or Read & Write if you want to create snapshots.

3. Configure your editor

Add the MCP server to your editor's config. Replace /path/to/hetzner-mcp with the actual path where you cloned the repo.

Edit your config file:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

• Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "hetzner": {
      "command": "/path/to/hetzner-mcp/.venv/bin/python",
      "args": ["/path/to/hetzner-mcp/server.py"],
      "env": {
        "HETZNER_API_TOKEN": "your-token-here",
        "PYTHONUNBUFFERED": "1"
      }
    }
  }
}

Restart Claude Desktop to load the server.

Add globally with one command:

claude mcp add hetzner \
  -s user \
  -e HETZNER_API_TOKEN=your-token-here \
  -- /path/to/hetzner-mcp/.venv/bin/python /path/to/hetzner-mcp/server.py

Or add manually to ~/.claude.json:

{
  "mcpServers": {
    "hetzner": {
      "command": "/path/to/hetzner-mcp/.venv/bin/python",
      "args": ["/path/to/hetzner-mcp/server.py"],
      "env": {
        "HETZNER_API_TOKEN": "your-token-here"
      }
    }
  }
}

For project-scoped setup, add to .mcp.json in the project root instead.

Edit the config file:

• Global: ~/.cursor/mcp.json

• Project: .cursor/mcp.json (in repo root)

{
  "mcpServers": {
    "hetzner": {
      "command": "/path/to/hetzner-mcp/.venv/bin/python",
      "args": ["/path/to/hetzner-mcp/server.py"],
      "env": {
        "HETZNER_API_TOKEN": "your-token-here"
      }
    }
  }
}

Or go to Settings → MCP in Cursor to add it via the UI.

Add to your workspace at .vscode/mcp.json:

{
  "mcpServers": {
    "hetzner": {
      "command": "/path/to/hetzner-mcp/.venv/bin/python",
      "args": ["/path/to/hetzner-mcp/server.py"],
      "env": {
        "HETZNER_API_TOKEN": "your-token-here"
      }
    }
  }
}

Or add to your user settings.json:

{
  "mcp.servers": {
    "hetzner": {
      "command": "/path/to/hetzner-mcp/.venv/bin/python",
      "args": ["/path/to/hetzner-mcp/server.py"],
      "env": {
        "HETZNER_API_TOKEN": "your-token-here"
      }
    }
  }
}

Edit the config file:

• macOS: ~/.codeium/windsurf/mcp_config.json

• Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json

{
  "mcpServers": {
    "hetzner": {
      "command": "/path/to/hetzner-mcp/.venv/bin/python",
      "args": ["/path/to/hetzner-mcp/server.py"],
      "env": {
        "HETZNER_API_TOKEN": "your-token-here"
      }
    }
  }
}

Or go to Plugins → Manage plugins → View raw config.

4. Try it out

Restart your editor and try: "Run a health check on my Hetzner servers".

Available Tools

Security

Your API token is stored in your local editor config file — it is never included in conversations or sent to any LLM provider. The MCP server runs locally on your machine and communicates with your editor via stdio.

For extra safety:

• Use a read-only API token if you don't need write operations

• Rotate your token regularly via Hetzner Cloud Console

• The .gitignore ensures .env files are never committed

Requirements

• Python 3.10+

• A Hetzner Cloud account with an API token

License

MIT