Can I use Hetzner Cloud as a CLI?

Yes. KosmoKrator exposes a Hetzner Cloud CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Hetzner Cloud through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Hetzner Cloud tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Hetzner Cloud credentials stored?

Hetzner Cloud credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Hetzner Cloud MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

productivity

Hetzner Cloud MCP Integration for CrewAI

Connect Hetzner Cloud to CrewAI through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 6 read 1 write Bearer token auth

Submit Hetzner Cloud feedback View package source

Connect Hetzner Cloud to CrewAI

Expose KosmoKrator integrations to CrewAI workers as scoped local tools.

Wrap kosmo integrations:call for specific tasks or connect workers to a local MCP gateway. The gateway is local, scoped to this integration, and starts with --write=deny so CrewAI can inspect read-capable tools without receiving write access by default.

Hetzner Cloud MCP Config for CrewAI

Use per-worker integration scopes to avoid giving every worker every tool.

{
  "mcpServers": {
    "kosmokrator-hetzner": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=hetzner",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=hetzner --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Hetzner Cloud instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Hetzner Cloud Tools Visible to CrewAI

CrewAI sees stable MCP tool names generated from the Hetzner Cloud integration catalog.

MCP tool	Source function	Type	Description
`integration__hetzner__hetzner_list_servers`	`hetzner.hetzner_list_servers`	Read	List Hetzner Cloud servers. Supports pagination with per_page and page parameters.
`integration__hetzner__hetzner_get_server`	`hetzner.hetzner_get_server`	Read	Get details for a specific Hetzner Cloud server by ID.
`integration__hetzner__hetzner_create_server`	`hetzner.hetzner_create_server`	Write	Create a new Hetzner Cloud server with specified name, type, and image.
`integration__hetzner__hetzner_list_volumes`	`hetzner.hetzner_list_volumes`	Read	List Hetzner Cloud volumes. Supports pagination with per_page and page parameters.
`integration__hetzner__hetzner_list_networks`	`hetzner.hetzner_list_networks`	Read	List Hetzner Cloud networks. Supports pagination with per_page and page parameters.
`integration__hetzner__hetzner_list_ssh_keys`	`hetzner.hetzner_list_ssh_keys`	Read	List Hetzner Cloud SSH keys. Supports pagination with per_page and page parameters.
`integration__hetzner__hetzner_get_current_user`	`hetzner.hetzner_get_current_user`	Read	Get the profile of the currently authenticated Hetzner Cloud user. Useful for verifying credentials and displaying account information.

Related Hetzner Cloud Pages

Hetzner Cloud CLIUse direct JSON commands instead of MCP discovery. Hetzner Cloud MCPFull gateway reference and MCP tool names. KosmoKrator for CrewAIClient-level gateway setup.