Feature Request: Native Hetzner Cloud Integration / Extension for Remote Development

Feature request for product/service

3rd Party Extensions

Describe the request

It would be very useful if Cursor had a native Hetzner Cloud integration (or an official extension) for connecting to and developing on Hetzner servers.
Currently, connecting Cursor to a Hetzner server requires manually configuring SSH. This works, but the process could be significantly streamlined through the Hetzner Cloud API.
Hetzner Cloud is commonly used by developers for VPS hosting, self-hosting, development environments, Docker deployments, and production servers.
SSH already provides the underlying remote connection, so this integration would not need to replace Cursor’s existing SSH functionality. Instead, it could use the Hetzner Cloud API for server discovery and configuration, then use SSH for the actual remote development session.

Hey, thanks for the feature request. The idea makes sense: avoid manually editing ~/.ssh/config and fetch the server list directly via the Hetzner Cloud API.

Right now we don’t have plans for a native integration with cloud providers like Hetzner or anyone else, and I can’t promise it. But your workflow is still doable without core changes. You can split it into 1 auth plus server listing via the Hetzner API, 2 generating an SSH config, 3 handing it off to the existing Remote-SSH flow. You can ship this today as a third-party extension or an MCP server. If you’re familiar with MCP, that can be a quick way to get provider-aware discovery while the idea gets votes.

I’ve left the request open so others can vote. The more interest in the thread, the clearer the priority.