hetzner-code-mcp
Related Servers
Alternatives to hetzner-code-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables 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.6351 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables interaction with Hostinger's services through 111 OpenAPI tools, deployment helpers, and agent-navigation tools, with built-in safety defaults.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to manage and monitor Hetzner Cloud infrastructure, including servers, firewalls, networks, and snapshots, while keeping the API token local and secure.MIT
- AlicenseBqualityDmaintenanceEnables conversational management of Hetzner Cloud, DNS, and Storage Box infrastructure through 137 MCP tools for CRUD operations and actions like server power control, DNS zone management, and storage box snapshots.100MIT
- AlicenseNot gradedqualityFmaintenanceEnables interaction with the complete Cloudflare API using a codemode pattern that allows agents to search the OpenAPI spec and execute API calls via JavaScript. This approach minimizes token usage by keeping the massive specification on the server and only returning relevant results.12 npm129Apache 2.0
- AlicenseAqualityFmaintenanceEnables AI models to dynamically create and execute their own custom tools through a meta-function architecture, supporting JavaScript, Python, and Shell runtimes with sandboxed security and human approval flows.510MIT
TDQS
Scored across 3 tools
The three tools map cleanly to discover (hetzner_search), read (hetzner_query), and mutate (hetzner_execute). Although hetzner_execute also permits GET, the descriptions explicitly direct pure reads to hetzner_query, leaving no real ambiguity about which tool to pick.
All tools use the same hetzner_ prefix followed by a clear action verb (search, query, execute). The pattern is predictable and consistent throughout.
Three tools is exactly right for a generic API-wrapper server: one for reference lookup, one for safe reads, one for guarded writes. Each tool has a distinct, essential role and none feels redundant.
The surface covers the full lifecycle for Hetzner's Cloud, Storage Box, and Robot APIs: discovery via search, reads via query, and all mutations via execute with validation and billing/destructive guards. No obvious operation category is missing.