PluginBench
MCP Server
Active

io.github.lazyants/hetzner MCP Server

io.github.lazyants/hetzner

RepositoryRegistry
How to choose

What this kind of tool is for

  • Automate a build, test, or deployment step you repeat by hand.
  • Review or refactor code in an existing repository without leaving your agent.
  • Bridge an internal service or CLI into the agent toolset.

How to compare servers like this

Scope of control:
Repos and CI are hard to undo; prefer tools that ask before anything irreversible.
Environment fit:
Match the runtime it expects (Node, Python, a container) to what you actually run.
Maintenance signal:
Check the last-commit date — dev tooling that lags upstream breaks first.
Config surface:
Prefer tools whose environment-variable or config keys are documented plainly.

This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.

What is the io.github.lazyants/hetzner MCP server?

MCP server for the Hetzner Cloud API — servers, networks, volumes, firewalls, and more.

How to install io.github.lazyants/hetzner

Copy-paste configuration for popular MCP clients.

transport: stdio
Config generated by PluginBench — verify against the source before use.
~/Library/Application Support/Claude/claude_desktop_config.json
JSON config
{
  "mcpServers": {
    "hetzner": {
      "command": "npx",
      "args": [
        "-y",
        "@lazyants/hetzner-mcp-server"
      ]
    }
  }
}

Related MCP servers

MCP server for the Lexware Office API — invoices, contacts, articles, and vouchers.

6
TypeScript
View repository →

MCP server for the Transkribus REST API — collections, documents, HTR/OCR, and models.

1
TypeScript
View repository →

Cloudflare Workers MCP server: agent-loop-detector

0
View repository →

Cloudflare Workers MCP server: agent-trace-auditor

0
View repository →

Cloudflare Workers MCP server: a11y-scorer

0
View repository →

Cloudflare Workers MCP server: agent-memory

0
View repository →