Skip to main content
Glama
Sign In
mcp-hetzner

mcp-hetzner

by ginkelsoft-development
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to mcp-hetzner

No user-submitted related servers found.

    Related Servers

    • Hetzner MCP

      Xodus-CO
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables users to manage Hetzner Cloud resources including servers, load balancers, and volumes through natural language commands. It facilitates infrastructure operations such as resource creation, security configuration, and real-time pricing queries within AI-powered environments.
      290 npm
      1
      -

    • hetzner-mcp

      monk24215
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to operate a Hetzner estate end to end — Cloud servers, Cloudflare and Hetzner DNS, SSH hosts, and Coolify deployments, plus multi-step recipes — through 53 tools. Writes are dry-run until confirmed, protected servers refuse destructive calls, and every call is audited with secrets masked.
      290 npm
      1
      MIT

    • Hetzner MCP Server

      jurislm
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables management of Hetzner Cloud resources including servers, SSH keys, volumes, storage boxes, and live metrics through 40 tools.
      28 npm
      MIT

    • hetzner-mcp

      devinoldenburg
      A
      license
      Not graded
      quality
      A
      maintenance
      Model Context Protocol server for full Hetzner Cloud + Storage API automation. Exposes all official Hetzner operations as MCP tools so AI agents can manage servers, networking, load balancers, firewalls, volumes, DNS zones, and storage boxes from one server.
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3/5.0

    Scored across 137 tools

    Disambiguation5/5

    All tools have clearly distinct purposes through specific verb-noun combinations and detailed descriptions. Even for similar resources (e.g., load balancer services vs targets), the actions are unique and well-defined.

    Naming Consistency5/5

    Tool names follow a consistent pattern: prefix indicating service (cloud_, dns_, sb_, hetzner_) + verb + noun in snake_case. The verb tense is uniform (imperative present) and the structure is predictable across all 137 tools.

    Tool Count2/5

    With 137 tools, the server is extremely large and exceeds the typical scope for a single MCP server. While the tools are necessary for complete Hetzner API coverage, the count is far beyond the recommended range and would benefit from decomposition into separate servers per service domain.

    Completeness5/5

    The tool set offers comprehensive CRUD and lifecycle operations for all exposed Hetzner services: compute, networking, storage, DNS, firewalls, load balancers, and more. No obvious gaps are present for the intended domain coverage.

    Maintenance

    ActivityInactive
    ResponsivenessSyncing

    Resources