Do profiling tools work?

[psociety]

Setup:

• Unity: Windows 2022.3.62f3
• Package version: 9.7.0
• Editor: Visual Studio Code 1.121.0
• AI: GLM-4.7

I'm trying to have to profile the game (because it takes 8secs to load) but whenever it tries to call the profiling tools it seems to fail:

MCP server output:

INFO:     127.0.0.1:49682 - "POST /mcp HTTP/1.1" 200 OK
2026-05-24 08:54:26,877 - transport.plugin_hub - WARNING - [Ping] Failed to send ping to session 4d1ce8bc-7041-4930-bc94-675426a2bb20: Unexpected ASGI message 'websocket.send', after sending 'websocket.close'.. Connection likely dead.
2026-05-24 08:54:26,877 - transport.plugin_hub - INFO - Plugin session 4d1ce8bc-7041-4930-bc94-675426a2bb20 disconnected (1005)
INFO:     127.0.0.1:49682 - "POST /mcp HTTP/1.1" 200 OK
INFO:     127.0.0.1:50649 - "WebSocket /hub/plugin" [accepted]
INFO:     connection open
2026-05-24 08:54:31,900 - transport.plugin_hub - INFO - Plugin registered: city (8979a8f10c62d781)
INFO:     127.0.0.1:49682 - "POST /mcp HTTP/1.1" 200 OK
2026-05-24 08:55:11,892 - transport.plugin_hub - INFO - Plugin session f89be976-3d45-4479-950c-8e4c2d1ecc7d disconnected (1005)
INFO:     127.0.0.1:49682 - "POST /mcp HTTP/1.1" 200 OK
INFO:     127.0.0.1:64094 - "WebSocket /hub/plugin" [accepted]
INFO:     connection open
2026-05-24 08:55:16,912 - transport.plugin_hub - INFO - Plugin registered: city (8979a8f10c62d781)
INFO:     127.0.0.1:49682 - "POST /mcp HTTP/1.1" 200 OK
2026-05-24 08:55:56,899 - transport.plugin_hub - INFO - Plugin session 633bdda2-a8bd-48a3-96bf-6577c7d37e0b disconnected (1005)
INFO:     127.0.0.1:49682 - "POST /mcp HTTP/1.1" 200 OK
INFO:     127.0.0.1:54982 - "WebSocket /hub/plugin" [accepted]
INFO:     connection open
2026-05-24 08:56:01,922 - transport.plugin_hub - INFO - Plugin registered: city (8979a8f10c62d781)
INFO:     127.0.0.1:49682 - "POST /mcp HTTP/1.1" 200 OK
2026-05-24 08:56:41,912 - transport.plugin_hub - WARNING - [Ping] Failed to send ping to session bc4e8f3d-7ae6-4528-a0b0-f56d337c6514: Unexpected ASGI message 'websocket.send', after sending 'websocket.close'.. Connection likely dead.
2026-05-24 08:56:41,913 - transport.plugin_hub - INFO - Plugin session bc4e8f3d-7ae6-4528-a0b0-f56d337c6514 disconnected (1005)
INFO:     127.0.0.1:49682 - "POST /mcp HTTP/1.1" 200 OK
INFO:     127.0.0.1:51037 - "WebSocket /hub/plugin" [accepted]
INFO:     connection open

Having the MCP server to print a log about the tool being called would also probable be helpful on helping debug what's happening.

Do profiling tools work for you guys?

[tigran-sargsyan-w]

The profiler tooling does exist in current versions, but the log you posted looks more like a transport/session problem than a Unity Profiler problem.

The important lines are:

Unexpected ASGI message 'websocket.send', after sending 'websocket.close'
Plugin session ... disconnected (1005)

and then the plugin reconnects a few seconds later.

So the Unity plugin connection itself is repeatedly dying/re-registering. Any profiler request that is in flight during that disconnect can fail regardless of whether the Profiler API works.

I would first make sure the Unity package and the Python/MCP server are from the same release. I would especially avoid debugging package 9.7.0 against documentation/tools from a newer server.

On current versions there are explicit profiler commands, so a useful minimal test is:

unity-mcp profiler status
unity-mcp profiler frame-timing

Then:

unity-mcp profiler start

reproduce the slow load and finally:

unity-mcp profiler stop

If status / frame-timing already fail while the log shows WebSocket disconnects, I would debug the plugin connection first rather than the profiler.

If those commands work directly but the AI agent fails when invoking them, then the problem is probably on the MCP client/tool-call side.

So yes, profiling is supported now; the 1005 disconnect/reconnect loop in your log is the first thing I would isolate.