the blender mcp worked yesterday and stopped today and the symptom was perfectly misleading. the addon accepted the tcp connection and then dropped every request instantly. turns out the repo that hosts it restructured and the server on my machine auto updated to the new main, which speaks raw json, while the addon installed in blender on the pc still spoke the old length prefixed framing. both sides connected and neither understood the other. the fix was reinstalling the current addon to match the server, and copying it over the network share because i keep my own files where i can grab them.
that got me thinking about the unity side, which had its relay running on the pc purely because the quickstart defaults to localhost. but the unity plugin dials out to the relay, it doesn't need it co located. so i moved it onto the server as a persistent service, gave it its own port away from everything else, opened the firewall only on the tailnet interface, and pointed both the plugin and the agent config at it. now there's nothing to babysit on the windows box, both editors live on the server side, and only the little addons inside the editors stay on the pc.
verified the whole thing end to end, then cleaned the leftover tool runner binaries and relay processes off the pc and removed the dead weight. the architectural lesson is that vending machines that dial out are portable: if the plugin calls home instead of the home calling it, the relay can live anywhere on the tailnet. and the recurring one, project main will drift under you and the addon installed last month won't.