MCP Server as a Docker container accessible on a home network

[jarrah31]

Not sure if this is technically feasible or even desirable, but would it be possible to run the home-assistant-mcp server as a docker container that can be accessible from any machine on a home network?

My thoughts behind this is to build upon the excellent progress you've made enabling VS Code and its many agents to query Home Assistant via a local nodejs MCP server that interacts with the HA Vibecode Addon.

I use the Remote SSH extension to connect to my Home Assistant server so that I can directly edit yaml files within /config. The downside to doing this is that AI Agent extensions then install and run from the remote server, or in this case the SSH Addon within HA that allows remote SSH connections. This means that MCP servers have to run on the remote server rather than my local client (due to STDIO), and because the SSH addon is itself a cut down container, I can't install and run nodejs which means neither can I run MCP servers. As a result, being able to specify a remote streamable MCP server in the mcp.json / toml files would be very useful.

The big benefit here is that I can continue to use VS Code to manually view and edit my yaml files if desired (with AI assistance) whilst at the same time making tool calls to the vibecode MCP server / addon for extra context. I like to see the changes being made to my yaml files by AI agents using the diff view where I can view and approve the updates. Whilst I know the Vibecode addon can modify yaml files via tool calls, I just prefer having a more hands-on approach.

If this is possible I see it as being the best of both worlds, direct IDE yaml file edits with AI assistance and MCP tool calls to the HA addon!

This may be going too far away from the original Claude Cursor Agent idea so I understand if this isn't the way you want your excellent project to go.