Optionally connect to places other than localhost

[michaelnugent]

This change allows the user to select listening on 0.0.0.0 instead of only loopback. Loopback is left as the default and the python portion's default assumes the hardcoded port on localhost unless cli arguments are passed. Dockerfile (see #108 ) has been updated to pass cli arguments.

Added

• Network Interface Configuration in Unity MCP Bridge

  • Added toggle option to listen on all network interfaces (0.0.0.0) vs. loopback only (127.0.0.1)
  • Added display of available IP addresses in the editor window
  • Added persistence of network interface settings using EditorPrefs
  • Added helper method to discover available IP addresses on the machine

• Docker Support for UnityMcpServer

  • Added command-line parameters to specify Unity host and port
  • Added --unity-host parameter to connect to specific Unity Editor hostname/IP
  • Added --unity-port parameter to specify custom port
  • Added --log-level parameter to control logging verbosity
  • Added README.docker.md with Docker configuration instructions
  • Added configuration examples for both Docker and Podman

Changed

• Modified UnityMcpBridge to support binding to all interfaces
• Updated Dockerfile to use a flexible ENTRYPOINT that accepts command-line arguments
• Enhanced connection logging to show the host and port being used
• Updated UnityMcpServer to explicitly use command-line parameters
• Improved error messages with more diagnostic information

Security

• Added warning message when listening on all interfaces
• Default binding remains on loopback only (127.0.0.1) for security
• Added documentation about security implications of network exposure

[bhadrik]

I have created agent inside of Unity instead of managing MCP, check it out here.
https://github.com/bhadrik/unity-autopilot