Hetzner

Created By
dkruyt7 months ago
Overview

what is Hetzner?

Hetzner is a Model Context Protocol (MCP) server designed for interacting with the Hetzner Cloud API, enabling users to manage cloud resources through structured functions.

how to use Hetzner?

To use Hetzner, clone the repository from GitHub, install the necessary dependencies, and set up your Hetzner Cloud API token in a .env file. You can then start the server and interact with it using various commands.

key features of Hetzner?

  • List, create, and manage Hetzner Cloud servers
  • Manage volumes, firewall rules, and SSH keys
  • Simple API for language model interaction
  • Integration with Claude Code for direct resource management

use cases of Hetzner?

  1. Automating server management tasks in the Hetzner Cloud.
  2. Managing firewall rules for enhanced security.
  3. Creating and managing SSH keys for secure access.

FAQ from Hetzner?

  • What programming language is required to run Hetzner?

Python 3.11 or higher is required.

  • Is there a demo available for Hetzner?

Yes, a demo is available in the repository.

  • Can I use Hetzner with other programming languages?

Currently, it is designed for Python, but you can interact with the API using any language that can make HTTP requests.

Project Info
Created At
7 months ago
Updated At
7 months ago
Author Name
dkruyt
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago