@tumml3r No, the dropdowns are in a fixed order. But I did push an update today, currently waiting to be merged, that you can test and see if it works better with VSCode. Someone on our Discord said it did. Let me know if you get better performance with the MCP. I'll have to fix the VSCode dropdown / UI stuff separately.

Unity MCP Bridge stability test – call for testers

I just finished an update that should fix many/most/hopefully all port error and connection issues on both Mac and PC. It would be fantastic if any unity-mcp users could test it out before we merge it into main.

Install (no git needed)

Edit your Unity project’s Packages/manifest.json and change one line:

"com.coplaydev.unity-mcp": "https://github.com/dsarno/unity-mcp.git?path=/UnityMcpBridge#feat/bridge-stability"

In Unity

Open Window → Unity MCP and confirm the bridge starts (e.g., “UnityMcpBridge started on port 6400”).
If needed, click “Repair Python Env” once to rebuild the server venv (uses uv).
Click “Auto‑Setup” (button shows “Connected ✓” when clients are configured).

From your IDE (Cursor/Claude/VSCode)

Run a simple MCP call (e.g., read_console).
Make a trivial code change to trigger a domain reload and confirm the connection remains stable on the same port.

Revert when done (back to default repo)

Edit Packages/manifest.json back to:

"com.coplaydev.unity-mcp": "https://github.com/CoplayDev/unity-mcp.git?path=/UnityMcpBridge"

Clean up VSCode config #195

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions