Hetzner Cloud (unofficial)

Name: Hetzner Cloud (unofficial)
Author: mguttmann

de mguttmannversión 0.2.0i★ –iSe ejecuta en tu computadora

Nombre en el registroio.github.mguttmann/the-real-hetzner-mcp

Instalar

Resumen

Descripción del creador (original en inglés)

Unofficial MCP server for the Hetzner Cloud API: one typed tool per operation, read and write.

Los tres pilares de PopNx MCP

Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.

Opinión de usuariosiAún no hay reseñasLas reseñas se abrirán junto con las cuentas en una etapa posterior
Nuestras revisiones básicasi1 de 1 superadasRevisado con información pública; el código aún no se ha escaneado
UsoiMuy nuevo↓ 71/sem · ★ –

Qué puedes hacer con él

Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.

Conexión: Se ejecuta en tu computadora
Transporte: stdio
Categoría: Otros
Debes completar: HETZNER_API_TOKEN

Instalación

Elige la app de IA que usas y copia la configuración.

Antes de instalar

Revisiones básicas: 1 de 1 superadas
Se ejecuta en tu computadora con los permisos de tu usuario (archivos, red, apps).
Debes completar tú: HETZNER_API_TOKEN, HETZNER_READ_ONLY, HETZNER_CONFIRM_WRITES, HETZNER_DENY_TOOLS, LOG_LEVEL

Los valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.

Necesitas

npmNode.js instalado (para el comando npx)

¿Qué app usas?

ClaudeClaude CodeCursorVS CodeChatGPT

Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.

Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json

{
  "mcpServers": {
    "the-real-hetzner": {
      "command": "npx",
      "args": [
        "-y",
        "@mguttmann/hetzner-cloud-mcp"
      ],
      "env": {
        "HETZNER_API_TOKEN": "your-value",
        "HETZNER_READ_ONLY": "your-value",
        "HETZNER_CONFIRM_WRITES": "your-value",
        "HETZNER_DENY_TOOLS": "your-value",
        "LOG_LEVEL": "your-value"
      }
    }
  }
}

Ejecuta esto en tu terminal

claude mcp add the-real-hetzner --env HETZNER_API_TOKEN=your-value --env HETZNER_READ_ONLY=your-value --env HETZNER_CONFIRM_WRITES=your-value --env HETZNER_DENY_TOOLS=your-value --env LOG_LEVEL=your-value -- npx -y @mguttmann/hetzner-cloud-mcp

Completa los valores vacíos antes de ejecutarlo.

Abrir en Cursor

O copia la configuración tú

Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json

{
  "mcpServers": {
    "the-real-hetzner": {
      "command": "npx",
      "args": [
        "-y",
        "@mguttmann/hetzner-cloud-mcp"
      ],
      "env": {
        "HETZNER_API_TOKEN": "your-value",
        "HETZNER_READ_ONLY": "your-value",
        "HETZNER_CONFIRM_WRITES": "your-value",
        "HETZNER_DENY_TOOLS": "your-value",
        "LOG_LEVEL": "your-value"
      }
    }
  }
}

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Abrir en VS Code

O copia la configuración tú

Pégalo en .vscode/mcp.json de tu proyecto

{
  "servers": {
    "the-real-hetzner": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@mguttmann/hetzner-cloud-mcp"
      ],
      "env": {
        "HETZNER_API_TOKEN": "your-value",
        "HETZNER_READ_ONLY": "your-value",
        "HETZNER_CONFIRM_WRITES": "your-value",
        "HETZNER_DENY_TOOLS": "your-value",
        "LOG_LEVEL": "your-value"
      }
    }
  }
}

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.

Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.

Valores que debes completar

HETZNER_API_TOKEN secreto obligatorio env
Hetzner Cloud API token from the Cloud Console (project > Security > API tokens). The server can do exactly what this token allows; use a Read token if the client only needs to read.
HETZNER_READ_ONLY env
true: every tool that is not read-only, and hcloud_raw_request with a method other than GET, returns an error without sending a request. Any value other than true, 1, yes, false, 0, no or empty stops…
HETZNER_CONFIRM_WRITES env
true: every tool that is not read-only returns a preview unless the call carries confirm "YES". Friction against mistakes, not a security boundary.
HETZNER_DENY_TOOLS env
Comma-separated tool name globs (for example hcloud_delete_*,hcloud_raw_request) that always return an error. Deny hcloud_raw_request as well, otherwise denied endpoints stay reachable through it. A…
LOG_LEVEL env
Log level of the JSON logs on stderr.

Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.

Qué puede hacer

Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.

Revisiones básicasi

Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 8 nov 2026

✓ Superada
El creador coincide con el repo
El nombre en el registro se verificó con la cuenta de GitHub mguttmann, dueña del repo
… Aún sin revisar
Sigue en mantenimiento
Todavía no hemos leído este repo en GitHub
… Aún sin revisar
Tiene licencia
Todavía no hemos leído este repo en GitHub
– No aplica
El endpoint responde
Este se ejecuta en tu computadora; no hay endpoint en internet
– No aplica
Inicio de sesión con OAuth
Se ejecuta en tu computadora y usa ajustes locales en su lugar
… Aún sin revisar
Sin instrucciones ocultas en las descripciones de herramientas
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet

Comparado con otros en Otrosi

Más estrellas que el 0% de los otros 18609 servidores de esta categoría
Publicado en el registro más recientemente que el 76% de los otros 18609 servidores de esta categoría
Revisiones básicas iguales o mejores que el 100% de los otros 18609 servidores de esta categoría

Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.

Preguntas frecuentes

¿Es seguro Hetzner Cloud (unofficial)?

Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.

¿Qué claves o códigos necesita?

Debes completar: HETZNER_API_TOKEN

¿Se ejecuta en mi computadora o en la nube?

Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).

¿Sigue en mantenimiento?

El repo de GitHub cambió por última vez –, y la última versión (0.2.0) llegó al registro hace 12 días.

¿Qué apps pueden usarlo?

Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Node.js en tu computadora.

¿Qué puedo usar en su lugar?

En la misma categoría: Spec Driven Development, Remote Desktop Commander, dsh-novel-writer — 网文写作体检

Alternativas

Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.

Cómo leer una tarjeta:↓ Descargas por semanai★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi

Spec Driven Development

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

de formulahendryInicial↓ 66/sem★ 440Actualizado hace 14 meses

Se ejecuta en tu computadora

Instalar

Remote Desktop Commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

de desktop-commanderEn crecimiento★ 211Actualizado hace 3 días

Se ejecuta en la nube✓ desktopcommander.app

Instalar

dsh-novel-writer — 网文写作体检

Offline 21-tool Chinese web-novel style, plot and continuity audits, plus per-book cleanup.

de siweinaInicial↓ 1,4 mil/semActualizado hoy

Se ejecuta en tu computadora

Instalar

README del creador

Abrir el README

Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.

the-real-hetzner-mcp

An unofficial local Model Context Protocol (MCP) server (stdio) for the Hetzner Cloud API: every operation of the vendored Hetzner Cloud API specification as a typed tool, read and write, plus hand-tuned wrappers for the common server operations. npm package: @mguttmann/hetzner-cloud-mcp.

Unofficial project. This server is not affiliated with, endorsed by, sponsored by or supported by Hetzner Online GmbH. "Hetzner" is a trademark of Hetzner Online GmbH. The vendored API specification (specs/cloud.spec.json) is Hetzner's and is not covered by this project's MIT License. See NOTICE.

Maintenance status

Maintained on a best-effort basis by one maintainer (@mguttmann) in spare time. There is no support contract and no guaranteed response time.
Security fixes take priority over features. Report vulnerabilities privately through GitHub private vulnerability reporting, never in a public issue; see SECURITY.md.
Only the latest minor release gets fixes (SECURITY.md lists the supported versions).
Dependency updates come from Dependabot; CI fails when a runtime dependency has a known high or critical advisory.
Releases are built and published by GitHub Actions from a tag on main, with a CycloneDX SBOM, SHA256SUMS and build provenance (CHANGELOG.md lists the changes).
Issues and pull requests are welcome. Tool names, parameters and environment variables are kept stable between releases; see AGENTS.md for the contract rules.

Features

Full coverage of the Hetzner Cloud API via codegen from specs/cloud.spec.json (one generated tool per operation), plus hand-tuned wrappers for the common server operations. The exact tool list and count are pinned by tests/tools-contract.test.ts against tests/snapshots/tools-contract.json.
hcloud_raw_request as a generic escape hatch for any endpoint.
Capped 429 backoff, automatic pagination with a soft-cap, action polling with a wall-clock budget (see Timeouts and retries).
Optional write guard HETZNER_CONFIRM_WRITES=true: every tool that is not read-only returns a preview (tool name and input) unless the call carries confirm: "YES".
Optional operator switches HETZNER_READ_ONLY=true (only read-only tools and GET through hcloud_raw_request run) and HETZNER_DENY_TOOLS (tool name globs that always return an error). Both leave the tool list and the schemas unchanged.

Out of Scope

Not covered: Hetzner Robot (the dedicated-server API), Hetzner DNS (the standalone DNS product, a separate API from Cloud DNS) and Hetzner Storage Boxes. They are not part of the Cloud API and the codegen has no spec for them.

Covered: Cloud DNS zones and RRSets (/v1/zones) are part of the Cloud API spec, so they are in scope through the generated tools.

Installation

Requires Node.js 22.12 or newer (engines in package.json; the CI matrix in .github/workflows/ci.yml tests the floor and the current Node lines).

Do not install 0.1.x. npm versions below 0.2.0 (0.1.0 and 0.1.1) are affected by a path-injection vulnerability that is fixed in 0.2.0, see SECURITY.md.

From npm (0.2.0 or newer)

The package name is exactly @mguttmann/hetzner-cloud-mcp; packages with similar names are not from this project.

npm install -g "@mguttmann/hetzner-cloud-mcp@>=0.2.0"

The version range makes npm refuse the vulnerable 0.1.x versions. If npm reports that no matching version exists, 0.2.0 is not published yet: install from a pinned git commit instead. In your MCP client config the command is then just hetzner-cloud-mcp (no path needed).

With npx (no global install)

npx -y "@mguttmann/hetzner-cloud-mcp@>=0.2.0"

MCP clients start it the same way, see Variant C. Keep the version range: without it npx would take whatever version npm serves as latest.

From the MCP Registry

Once listed, the server is in the official MCP Registry as io.github.mguttmann/the-real-hetzner-mcp, with the npm package above as its package. Clients that install from the registry use the same npm package.

From a pinned git commit

git clone https://github.com/mguttmann/the-real-hetzner-mcp.git

cd the-real-hetzner-mcp git checkout npm ci npm run build

Pin a full commit SHA, not a branch name: the commit of the v0.2.0 tag (git rev-list -n 1 v0.2.0) or a later commit on main. npm ci installs exactly the committed lockfile.

Setup

With the npm package, set the variables in the env block of your MCP client configuration (see MCP Connector Setup); the package ships no .env file. In a git checkout:

cp .env.example .env

Add HETZNER_API_TOKEN to .env (Read & Write token from the Hetzner Cloud Console)

npm run refresh-spec and npm run generate are not part of the setup: they change the tool surface (see Spec Updates).

The server reads its configuration from the environment. At startup it also loads the .env file in the package directory (next to package.json, dotenv), never one from the current working directory; variables that are already set win. A deployment can pass the file explicitly instead, from any working directory: node --env-file=/path/to/.env dist/index.js.

Optional smoke test against the real API (four read-only calls):

npm run test:live

Configuration

Only HETZNER_API_TOKEN is required. The defaults below are pinned by tests/config.test.ts. A numeric value that is not a positive number, and an unknown boolean or log level, falls back to the default. Exceptions that stop the server at startup instead: an invalid HETZNER_API_BASE and an unknown HETZNER_READ_ONLY value.

Variable	Default	Meaning
`HETZNER_API_TOKEN`	(required)	Hetzner Cloud API token, sent as a bearer token on every request. The server can do exactly what this token allows.
`HETZNER_API_BASE`	`https://api.hetzner.cloud/v1`	API base URL. Must be `https`; plain `http` only for `localhost`, `127.0.0.1` or `::1`. Any other value stops the server at startup. Override only for tests or a local fake upstream.
`HETZNER_CONFIRM_WRITES`	`false`	`true`, `1` or `yes`: every tool that is not read-only returns a preview unless the call carries `confirm: "YES"`.
`HETZNER_READ_ONLY`	`false`	`true`, `1` or `yes`: every tool that is not annotated read-only, and `hcloud_raw_request` with a method other than `GET`, returns `isError` without sending a request. Checked before the confirm guard. Tool list and schemas are unchanged. Any value other than `true`, `1`, `yes`, `false`, `0`, `no` or empty stops the server at startup.
`HETZNER_DENY_TOOLS`	(empty)	Comma-separated tool name globs (`` any characters, `?` one character, whole name, case-sensitive), for example `hcloud_delete_,hcloud_raw_request`. A matching tool returns `isError` without sending a request, read-only tools included. Tool list and schemas are unchanged. Patterns use the server's own `hcloud_*` names, not a gateway-prefixed name; a pattern that matches no tool stops the server at startup. Denying a tool does not block its endpoint through `hcloud_raw_request`, so deny `hcloud_raw_request` as well, otherwise every denied endpoint stays reachable through it.
`LOG_LEVEL`	`warn`	`debug`, `info`, `warn` or `error`. Logs are JSON on stderr; stdout carries the MCP protocol.
`HTTP_TIMEOUT_MS`	`30000`	Wall-clock budget for one API request, all attempts and retry delays included.
`HTTP_MAX_RETRY_DELAY_MS`	`10000`	Longest single retry delay. A 429 whose `Retry-After` asks for more is returned at once as an error.
`ACTION_POLL_TIMEOUT_MS`	`45000`	Wall-clock budget of a `wait: true` call, measured from the start of the call (write request, poll requests and their retries included). Also the ceiling for the `timeout_ms` argument of `hcloud_wait_action`.
`ACTION_POLL_INTERVAL_MS`	`2000`	Pause between two polls. The `interval_ms` argument of `hcloud_wait_action` cannot go below 1000 or this value, whichever is lower.
`PAGINATION_MAX_ITEMS`	`500`	Soft cap on the items an auto-paginated list collects; a capped list reports `truncated: true`.
`PAGINATION_MAX_PAGES`	`10`	Soft cap on the pages an auto-paginated list requests.
`MAX_OUTPUT_BYTES`	`8388608`	Largest tool result text in bytes, counted as sent (JSON-escaped). A longer result is cut and ends with `[output truncated by MAX_OUTPUT_BYTES=...]`. Values above the default are lowered to it, so one result line stays below the 10 MiB stdio limit.
`PAGINATION_TIMEOUT_MS`	`45000`	Wall-clock budget of one auto-paginated list. When it ends, the pages read so far come back with `truncated: true` and a `note`.
`MCP_SERVE_MODERN_PROTOCOL`	`false`	`true`, `1` or `yes`: also serve the MCP 2026-07-28 revision over stdio (see MCP protocol). A client that opens with `initialize` gets the same 2025-era session as with `false`.

Development only: RUN_LIVE_TESTS=1 enables tests/live-smoke.test.ts (set by npm run test:live), and HETZNER_LIVE_SMOKE_ANCHORS optionally names servers that test expects to find.

Timeouts and retries

Retries: a 429 is retried after Retry-After, or after a short backoff when the header is missing (Hetzner refills one request per second; RateLimit-Reset is the time the bucket is full again and is not used as a delay). A 5xx is retried with backoff, except for POST, which may already have been processed. With the defaults one tool call answers within about max(HTTP_TIMEOUT_MS, ACTION_POLL_TIMEOUT_MS) (tests/call-budget.test.ts measures this), so it stays below a 60 s client call timeout, common in MCP clients and gateways. Keep that relation if you raise the values. Auto-paginated lists run one request per page within PAGINATION_TIMEOUT_MS; when that budget ends, the pages read so far come back with truncated: true and a note, never as a list that looks complete.

When polling fails or the budget runs out after a successful write, the tool returns the write response (for example the new resource id and a one-time root_password) with polling_timed_out: true, plus polling_error if polling failed.

MCP protocol

The server speaks MCP over stdio only and opens no network port.

Protocol revisions: a client that asks for 2024-11-05, 2025-03-26, 2025-06-18 or 2025-11-25 gets that revision back; a client that asks for a newer one (for example 2026-07-28) in initialize gets 2025-11-25 (tests/server.test.ts).
2026-07-28 is opt-in: with MCP_SERVE_MODERN_PROTOCOL=true the server also answers a client that opens with server/discover and serves it the 2026-07-28 revision, with the same tools. A client that opens with initialize still gets the 2025-era session above (tests/serve-protocol.test.ts). The default is false: a client in auto mode (such as the python mcp client) would switch to the new revision as soon as it is offered, so turn it on only after checking the client. See docs/adr/0001-mcp-sdk-v2.md.
Message size limit: one inbound JSON-RPC message (one stdin line) may be at most 10 MiB, the MCP SDK's stdio limit (tests/transport-lifecycle.test.ts). A longer line closes the transport: the server logs mcp transport error on stderr and exits with code 1. Keep large arguments (for example user_data) well below that size. Outbound, a tool result is cut at MAX_OUTPUT_BYTES (at most 8 MiB, tests/output-cap.test.ts) and then ends with an [output truncated by MAX_OUTPUT_BYTES=...] marker.

MCP Connector Setup (Claude Desktop / Claude Code)

Append to your cli

Solo se muestra el principio; lee el resto en el repo

Hetzner Cloud (unofficial)

Resumen

Los tres pilares de PopNx MCP

Qué puedes hacer con él

Instalación

Antes de instalar

Valores que debes completar

Qué puede hacer

Revisiones básicasi

El creador coincide con el repo

Sigue en mantenimiento

Tiene licencia

El endpoint responde

Inicio de sesión con OAuth

Sin instrucciones ocultas en las descripciones de herramientas

Comparado con otros en Otrosi

Preguntas frecuentes

Alternativas

Spec Driven Development

Remote Desktop Commander

dsh-novel-writer — 网文写作体检

README del creador

the-real-hetzner-mcp

Maintenance status

Features

Out of Scope

Installation

From npm (0.2.0 or newer)

With npx (no global install)

From the MCP Registry

From a pinned git commit

Setup

Add HETZNER_API_TOKEN to .env (Read & Write token from the Hetzner Cloud Console)

Configuration

Timeouts and retries

MCP protocol

MCP Connector Setup (Claude Desktop / Claude Code)