Just want to let you know I had a lot of disconnects from the MCP bridge with Codex. So I asked codex to fix this issue and it is solved. Using your 1.14.1 version.
This is what I got after:
The bridge was failing because Codex had accumulated 13 stale node.exe **\server\build\index.js processes. They filled 6505-6509, but the Godot editor plugin polls 6505-6514, while the Node MCP server only scanned up to 6509. New Codex MCP launches could not bind a port, so the tool reported “Godot editor is not connected.”
Changed:
- Expanded the MCP server scan range to
6505-6514in [godot-connection.ts (line 15)](**\\server\\src\\godot-connection.ts:15). - Added shutdown cleanup for stdio close, stdin close/end,
SIGINT, andSIGTERMin [index.ts (line 71)](**\\server\\src\\index.ts:71) and [index.ts (line 167)](**\\server\\src\\index.ts:167), so abandoned MCP processes should release their WebSocket listener instead of lingering. - Rebuilt
**\server\build. - Stopped the 13 stale Godot-MCP Node bridge processes.