hcloud-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HCLOUD_TOKEN | Yes | Hetzner Cloud API token (project -> Security -> API Tokens) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_serversC | List all servers |
| create_serverD | Create a new server |
| delete_serverC | Delete a server |
| change_server_typeA | Change the type of a server (scales resources). Server must be powered off. |
| power_on_serverC | Power on a server |
| power_off_serverC | Power off a server (hard) |
| reboot_serverC | Reboot a server (soft) |
| shutdown_serverC | Shutdown a server (soft) |
| reset_serverC | Reset a server (hard) |
| update_serverC | Update a server (name, labels) |
| attach_isoC | Attach an ISO to a server |
| detach_isoC | Detach an ISO from a server |
| attach_server_to_networkC | Attach a server to a network |
| detach_server_from_networkC | Detach a server from a network |
| list_load_balancersB | List all load balancers |
| create_load_balancerD | Create a new load balancer |
| delete_load_balancerC | Delete a load balancer |
| update_load_balancerC | Update a load balancer (name, labels) |
| add_load_balancer_targetC | Add a target to a load balancer |
| remove_load_balancer_targetC | Remove a target from a load balancer |
| add_load_balancer_serviceC | Add a service to a load balancer |
| delete_load_balancer_serviceC | Delete a service from a load balancer |
| list_networksC | List all networks |
| create_networkC | Create a new network |
| delete_networkC | Delete a network |
| update_networkC | Update a network (name, labels) |
| add_network_subnetC | Add a subnet to a network (e.g. for private networking 10.0.0.0/16 in a zone) |
| delete_network_subnetB | Delete a subnet from a network (detach servers from it first) |
| list_volumesB | List all volumes |
| create_volumeD | Create a new volume |
| update_volumeC | Update a volume (name, labels) |
| attach_volumeC | Attach a volume to a server |
| detach_volumeC | Detach a volume |
| delete_volumeA | Delete a volume (must be detached; all data destroyed) |
| list_firewallsB | List all firewalls |
| create_firewallD | Create a new firewall |
| update_firewallC | Update a firewall (name, labels) |
| delete_firewallB | Delete a firewall (must not be in use) |
| list_floating_ipsB | List all floating IPs |
| create_floating_ipC | Create a floating IP |
| update_floating_ipC | Update a floating IP (description, labels) |
| assign_floating_ipC | Assign a floating IP to a server |
| unassign_floating_ipC | Unassign a floating IP |
| delete_floating_ipC | Delete a floating IP (unassigns from server if attached) |
| list_primary_ipsA | List all Primary IPs (static IPs bound to a datacenter, assignable to one server) |
| create_primary_ipB | Create a Primary IP (datacenter-scoped; server must be off to assign). Provide datacenter OR assignee_id (server). |
| get_primary_ipC | Get a single Primary IP by ID |
| update_primary_ipC | Update a Primary IP (name, labels) |
| delete_primary_ipA | Delete a Primary IP (unassigns from server if assigned; server must be off) |
| assign_primary_ipA | Assign a Primary IP to a server (server must be powered off) |
| unassign_primary_ipA | Unassign a Primary IP from its server (server must be powered off) |
| list_ssh_keysB | List all SSH keys |
| create_ssh_keyC | Create a new SSH key |
| update_ssh_keyC | Update an SSH key (name, labels) |
| delete_ssh_keyC | Delete an SSH key |
| list_locationsC | List all locations |
| list_imagesC | List all images |
| list_server_typesB | List all server types |
| list_load_balancer_typesA | List all load balancer types (for create_load_balancer load_balancer_type) |
| list_datacentersB | List all datacenters (e.g. ash-dc1; where servers can be created) |
| list_actionsB | List actions (optionally filter by id, status); use to poll/wait for create/delete results |
| get_actionB | Get a single action by ID (e.g. to check progress or status after create/delete) |
| get_pricingC | Get all prices |
| list_placement_groupsB | List all placement groups |
| create_placement_groupC | Create a new placement group |
| delete_placement_groupC | Delete a placement group |
| update_placement_groupC | Update a placement group (name, labels) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 67 tools
Most tools have clearly distinct purposes targeting specific resources and actions, such as create_server vs. update_server. However, there is some potential overlap between power_off_server and shutdown_server (both stop a server) and between reboot_server and reset_server (both restart a server), which could cause minor confusion for an agent.
Tool names follow a highly consistent verb_noun pattern throughout, with clear action prefixes like create_, list_, update_, delete_, attach_, detach_, etc. All names use snake_case uniformly, making them predictable and easy to parse.
With 67 tools, the count is excessive for typical MCP server purposes, making it overwhelming for agents to navigate. While the server covers a broad cloud infrastructure domain, the toolset feels bloated and could benefit from consolidation or better scoping to reduce cognitive load.
The toolset provides comprehensive CRUD and lifecycle coverage for all major resources (servers, networks, load balancers, volumes, etc.), including create, list, update, delete, attach/detach, and power management operations. There are no obvious gaps, ensuring agents can handle full workflows without dead ends.