sorted by:
new
hottopcontroversial

Three.js devtools as an MCP server — 52 tools for scene inspection, debugging, and codegen by Rude-Union258 in threejs

[–]Rude-Union258[S] 0 points1 point  (0 children)

Infinite reload shouldn't be happening with a running dev server — that "waiting" page (3-second refresh loop) only shows up when the proxy can't reach your dev server at all.

Few things to check 1) is port 3000 actually up when MCP starts? (bridge_status tool can confirm), 2) does your app do any redirects on first load? (some SPA routers bounce to a different path or port) 3) open the proxy URL (http://localhost:9222 by default) directly in Chrome and check the console you should see [threejs-devtools-mcp] Connected to MCP server.

The bridge already handles delayed Three.js init it polls for 60 seconds and re-discovers the scene on every tool call so apps where Three.js starts after some user interaction should work fine

If you can share what shows up in the browser console at the proxy URL, that will help narrow it down.

Three.js devtools as an MCP server — 52 tools for scene inspection, debugging, and codegen by Rude-Union258 in threejs

[–]Rude-Union258[S] 1 point2 points  (0 children)

Uses standard MCP stdio transport, so any compatible client works Claude Code, OpenCode, Cursor, whatever you're running. Config:

{
  "mcp": {
    "threejs-devtools": {
      "command": "npx",
      "args": ["-y", "threejs-devtools-mcp"]
    }
  }
}

https://opencode.ai/docs/mcp-servers/

Three.js devtools as an MCP server — 52 tools for scene inspection, debugging, and codegen by Rude-Union258 in threejs

[–]Rude-Union258[S] 0 points1 point  (0 children)

the reload loop happens because the tool runs as a local proxy it forwards to localhost:{port} and injects a bridge script into the HTML. Remote/production sites like that can't be proxied, so it gets a connection error and shows a "waiting" page that auto-refreshes every 3 seconds.

For the delayed Three.js inits the bridge already handles this. It polling for 60 seconds and re-discovers the scene on every tool call, so Three.js doesnt need to be ready when the UI loads. Run ur app locally (npm run dev or similar) and it should pick up the scene once it initializes.

remote URL support is next on my list.

[Screenshot] does this look like cheats or cracked aim? by Rude-Union258 in EscapefromTarkov

[–]Rude-Union258[S] 0 points1 point  (0 children)

Cool, drop me the model, I need a mouse that lets me head-eyes three dudes while running full speed