MCP Hetzner Go

Created By
MahdadGhasemiana year ago
A Go Model Context Protocol (MCP) server for interacting with the Hetzner Cloud API.
Overview

what is MCP Hetzner Go?

MCP Hetzner Go is a Go Model Context Protocol (MCP) server designed for seamless interaction with the Hetzner Cloud API, enabling users to manage cloud resources effectively.

how to use MCP Hetzner Go?

To use MCP Hetzner Go, configure the server by creating a JSON file with your Hetzner Cloud token and the path to the Go executable. Then, build and run the client and server using the provided commands.

key features of MCP Hetzner Go?

  • Supports both read-only and read-write operation modes.
  • Allows management of various Hetzner Cloud resources such as servers, SSH keys, and load balancers.
  • Provides a linting tool for code quality checks.

use cases of MCP Hetzner Go?

  1. Managing cloud resources in a secure and controlled manner.
  2. Automating cloud operations through scripts and applications.
  3. Monitoring cloud resource states and configurations.

FAQ from MCP Hetzner Go?

  • What is the default operation mode?

The server starts in read-only mode by default, allowing only GET and LIST operations.

  • How can I enable write operations?

You can enable write operations by setting the configuration flag to read-write mode.

  • Is there a risk in enabling write mode?

Yes, enabling write mode allows changes to your Hetzner Cloud resources, so ensure proper access controls are in place.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MahdadGhasemian
Star
0
Language
Go
License
MIT 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)

2 days ago