I have been using Cursor a lot for programming and I feel like it would be an amazing pairing with Home Assistant. I have managed to SSH into Home Assistant via Cursor however that does not keep my Cursor configs (MCPs, etc) when I do it that way.
Ideally what I am looking for is a way to work on my Home Assistant config like I would would any other repo: using version control via git, make changes in a new branch, open an MR and and merge into main. Once that is done, Home Assistant would automatically pull the latest version of the code from GitHub.
My setup is:
Raspberry Pi 5 running Home Assistant
This is actually exposed via Cloudflare on a website so I can manage it remotely
Use Cursor as my IDE
GitHub for version control
Has anyone experimented with this? If so, how did you set it up?
This would be extremely interesting for me as well. I mean there is Studio Code Server, so getting Cursor to work over SSH should not be too difficult. But i tried and tried without success.
This might not be answering the original question involving version control, but with regards to getting Cursor to work over SSH, here’s how I managed:
In Home Assistant
In the standard SSH add-on, enable TCP forwarding (in UI: Configuration > Server > tcp_forwarding)
Note: Studio Code Server isn’t needed
Config SSH authentication as you wish and confirm you can connect
In Cursor:
Using the Remote-SSH extension, connect to the HA server (from command palette: Remote-SSH: Connect to Host)
Cursor will automatically install Cursor Server on your HA
server
Once installed, you should be able to open any HA folder!
The key sticking point is likely the TCP forwarding. Cursor installs its own server, but the problem seems to be whether Cursor can reach it afterwards.
Hey!
I’ve been working on exactly this kind of setup and ended up building a solution that connects Cursor IDE directly to Home Assistant through the MCP protocol.
It lets you:
edit and deploy automations right from Cursor,
version all configs and scripts via Git,
and communicate with Home Assistant through an on-board Agent (running on your Raspberry Pi).
Basically, it turns your Home Assistant setup into a developer-friendly workflow — you can treat it like any other codebase: branch → edit → commit → deploy, all without SSH or manual YAML uploads.