Hetzner Cloud MCP server
Hetzner Cloud in any MCP client, through Memtro: Hetzner Cloud does not publish this server. Memtro's Hetzner Cloud connector reads Hetzner Cloud through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
Hetzner Cloud project inventory: servers with type, location, IPs, status and traffic, volumes, networks, load balancers, firewalls and their rules, primary and floating IPs, and snapshots and backups. Can power a server on, shut it down, reboot, power off or reset it, snapshot, rename or delete it, and grow, attach, detach or delete a volume. One connection per project.
Reads
hetzner_list_serversServers in the Hetzner Cloud project: name, status (running, off…), type with cores, memory and disk, location, image, public and private IPs…hetzner_list_volumesBlock storage volumes: name, size, status, attached server id, location, filesystem and labels.hetzner_list_networksPrivate networks: IP range, subnets, how many servers and load balancers are attached, and labels.hetzner_list_load_balancersLoad balancers: type, location, public IP, algorithm, listening services (protocol and ports), number of targets, traffic and labels.hetzner_list_firewallsFirewalls with their rules (direction, protocol, port, source and destination ranges) and how many resources each is applied to.hetzner_list_ipsPrimary and floating IP addresses: the address, IPv4 or IPv6, what it is assigned to, location, whether blocked, and labels.hetzner_list_snapshotsSnapshots and backups (the project's own images, not Hetzner's public OS images): description, size, the server it came from, status and created date.
Acts, when you ask
These change something in Hetzner Cloud. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
hetzner_power_on_serverPowers on a Hetzner server that is off.hetzner_shutdown_serverShuts a Hetzner server down gracefully (an ACPI request to its OS), taking it offline for its users until powered on.hetzner_reboot_serverSoft-reboots a Hetzner server (an ACPI request to its OS); it is briefly offline.hetzner_power_off_serverCuts power to a Hetzner server at once, like pulling the plug: unsaved data may be lost.hetzner_reset_serverHard-resets a Hetzner server (cuts power and starts it again): unsaved data may be lost.hetzner_create_server_snapshotCopies a Hetzner server's disk into a new snapshot image, billed per GB each month until deleted in the Hetzner Console.hetzner_rename_serverRenames a Hetzner server (its name in the project, not its hostname inside the OS).hetzner_delete_serverPermanently deletes a Hetzner server and everything on its disk; it cannot be undone, and its backup images go with it.hetzner_resize_volumeGrows a Hetzner volume to a larger size, which raises its monthly price.hetzner_attach_volumeAttaches a Hetzner volume to a server in the same location.hetzner_detach_volumeDetaches a Hetzner volume from its server: the server loses that disk at once, so anything using it fails.hetzner_delete_volumePermanently deletes a Hetzner volume and its data; it cannot be undone.
Connect it
First connect Hetzner Cloud on Dashboard → Connections, then add Memtro to your client once. The Hetzner Cloud tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Hetzner Cloud connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › What servers do we run on Hetzner, and in which locations?
- › Which ports are open on the web firewall?
- › When was the last snapshot of the database server taken?
- › Reboot the staging-web-2 server
- › Grow the db-data volume to 200 GB
Questions
- Is this an official Hetzner Cloud MCP server?
- No. It is Memtro's MCP server with Memtro's Hetzner Cloud connector behind it: the connector reads Hetzner Cloud through its API with the credentials you connect on Dashboard → Connections, and Hetzner Cloud publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in Hetzner Cloud?
- Only when you ask, and only what it has been granted: power on a Hetzner server; shut down a Hetzner server gracefully; reboot a Hetzner server; power off a Hetzner server (hard); reset a Hetzner server (hard power cycle); take a snapshot of a Hetzner server; rename a Hetzner server; delete a Hetzner server permanently; grow a Hetzner volume; attach a Hetzner volume to a server; detach a Hetzner volume from its server; delete a Hetzner volume permanently. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.