
Three.Js DevTools MCP
- 80 repo stars
- Updated April 7, 2026
- DmitriyGolub/threejs-devtools-mcp
Three.js DevTools MCP is an MCP server that lets AI agents inspect and edit live Three.js scenes, materials, shaders, and lights in real time.
About
Three.js DevTools MCP proxies your local Three.js app through a bridge so Claude Code, Cursor, and similar hosts can inspect and mutate the live WebGL scene instead of guessing from static code. developers shipping 3D portfolios, product configurators, or lightweight games use it when shader bugs and lighting only show up in the running renderer. Environment variables cover dev server port, bridge port, headless CI runs, and optional Chrome path. The workflow assumes an npm-based Three project already serving locally. It complements code review skills by giving the agent runtime visibility. Skillselion places it on build frontend with secondary ship perf and operate iterate because tuning and fixes span multiple journey steps.
- Real-time inspect and edit of Three.js scenes, materials, shaders, and lights from MCP agents
- Auto-detects dev port from package.json or DEV_PORT; BRIDGE_PORT default 9222
- Browser modes: auto-open, BROWSER=none, HEADLESS=true for CI, custom CHROME_PATH
- Stdio MCP via npx threejs-devtools-mcp 0.2.1
Three.Js DevTools MCP by the numbers
- Data as of Jul 27, 2026 (Skillselion catalog sync)
claude mcp add --env DEV_PORT=YOUR_DEV_PORT --env BRIDGE_PORT=YOUR_BRIDGE_PORT --env BROWSER=YOUR_BROWSER --env HEADLESS=YOUR_HEADLESS --env CHROME_PATH=YOUR_CHROME_PATH threejs-devtools-mcp -- npx -y threejs-devtools-mcpAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| repo stars | ★ 80 |
|---|---|
| Package | threejs-devtools-mcp |
| Transport | STDIO |
| Auth | None |
| Last updated | April 7, 2026 |
| Repository | DmitriyGolub/threejs-devtools-mcp ↗ |
What it does
Debug Three.js scenes from your agent by inspecting and editing materials, shaders, lights, and scene graph in real time through a browser bridge.
Who is it for?
Best when you're building Three.js web experiences and want agent-assisted live debugging with familiar Chrome dev bridging.
Skip if: Non-Three stacks, native Unity/Unreal workflows, or teams that forbid local browser automation.
What you get
With the bridge running, your agent edits scene objects in real time against the proxied dev server, including headless CI when HEADLESS=true.
- Live MCP tools over proxied Three.js runtime
- Faster shader/material/light iteration without manual devtools-only sessions
By the numbers
- Package version 0.2.1
- Default bridge port 9222 documented in server.json
README.md
threejs-devtools-mcp
MCP server for inspecting and modifying Three.js scenes in real time — 59 tools for objects, materials, shaders, textures, animations, performance monitoring, memory diagnostics, and code generation.
Zero changes to your project. Works with vanilla Three.js, React Three Fiber, and any framework.

Setup
1. Add the MCP server
Claude Code
claude mcp add threejs-devtools-mcp -- npx threejs-devtools-mcp
Claude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"threejs-devtools-mcp": {
"command": "npx",
"args": ["-y", "threejs-devtools-mcp"]
}
}
}
Cursor
Add to .cursor/mcp.json in your project:
{
"mcpServers": {
"threejs-devtools-mcp": {
"command": "npx",
"args": ["-y", "threejs-devtools-mcp"]
}
}
}
Or use the HTTP transport — see Cursor setup guide.
Windsurf
Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"threejs-devtools-mcp": {
"command": "npx",
"args": ["-y", "threejs-devtools-mcp"]
}
}
}
VS Code (Copilot)
Add to .vscode/mcp.json:
{
"servers": {
"threejs-devtools-mcp": {
"command": "npx",
"args": ["-y", "threejs-devtools-mcp"]
}
}
}
OpenCode
Add to opencode.json in your project:
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"threejs-devtools-mcp": {
"type": "local",
"command": ["npx", "-y", "threejs-devtools-mcp"],
"enabled": true
}
}
}
2. Start your dev server and open the browser
Start your Three.js dev server as usual (npm run dev). The MCP server auto-detects the port from package.json and opens a browser at localhost:9222 with the devtools bridge injected.
Keep the browser tab open. The MCP server talks to your scene through a WebSocket bridge. Close the tab = tools stop working.
3. Ask the AI about your scene
"show me the scene tree"
"why is my model invisible?"
"make the car red"
"check for memory leaks"
"what's my FPS?"
"generate a React component from character.glb"
In-browser overlay
A built-in devtools panel with live performance stats, interactive scene graph, material editor, and 3D object preview. Activated automatically or via the toggle_overlay tool.

Tip: name your objects
Unnamed objects show as (unnamed) in the scene tree. Named objects are easier to find and modify:
// Three.js
mesh.name = "player";
// React Three Fiber
<mesh name="player" geometry={geometry} material={material} />
Documentation
- Tools reference — all 59 tools with parameters
- Advanced setup — animations, scene export, configuration, transports
- Cursor setup — step-by-step guide for Cursor
- Token-efficient workflow — best practices for saving context
License
MIT
Recommended MCP Servers
How it compares
Browser-linked Three.js MCP debugger, not a generic DOM scraper or static AST linter.
FAQ
Who is Three.Js DevTools MCP for?
Frontend and creative-coding developers using Three.js who already run MCP agents and local dev servers.
When should I use Three.Js DevTools MCP?
Use it while building or polishing 3D web apps whenever you need live scene, material, shader, or light edits from the agent.
How do I add Three.Js DevTools MCP to my agent?
Register stdio MCP (npx threejs-devtools-mcp), set DEV_PORT if needed, configure BRIDGE_PORT/HEADLESS, then point the server at your running Three.js dev app.