Skip to main content
Glama

Related Servers

Alternatives to hetzner-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables Claude Code to manage Hetzner Cloud servers, including creating, deleting, powering on/off, and rebooting servers, as well as managing SSH keys and listing resources.
      14
      46 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables managing a self-hosted Coolify PaaS from Claude, Cursor, or any MCP client through 45 tools for deploying, rolling back, debugging, and operating applications, databases, services, projects, and environments in plain English. Destructive operations pause for human confirmation and secrets stay masked.
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables agentic administration of Infomaniak accounts via Claude, offering 169 tools for web hosting, mail, domains, DNS, and more, with a strict two-phase commit for safe mutations.
      100
      3 npm
      MIT
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables Claude to manage a Proxmox cluster through chat: inventory, power control, configuration changes, VM/container creation and cloning, snapshots, network/firewall/cluster visibility, guest command execution, and file writes via the QEMU Guest Agent.
      22 npm
      MIT

    TDQS

    B3.4/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool has a distinct job: registry listing, registration, removal, fleet inventory, audit history, and capability reporting. The only mild overlap is hz_host_list vs hz_fleet_overview (registry SSH targets vs Hetzner cloud servers with costs), but descriptions make the distinction clear enough.

    Naming Consistency4/5

    Most tools follow a hz_<resource>_<action> snake_case pattern (hz_host_list, hz_host_register, hz_host_remove, hz_fleet_overview), which is predictable. Deviations are minor: audit_log lacks the hz_ prefix and hz_capabilities is resource-only with no verb.

    Tool Count5/5

    Six tools is well-scoped for a registry-plus-inventory server; each earns its place (three host CRUD operations, one fleet read, plus two meta/observability tools). Nothing feels redundant or padded.

    Completeness3/5

    Registry lifecycle is covered (list/register/replace/remove), but there is no get-single-host detail tool and no Hetzner server lifecycle operations (create, delete, power, resize, snapshots) despite the server's name implying cloud management. hz_capabilities hints modules may be toggled on, so the surface is intentionally partial but has notable gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues