Back to Browse
Free
Inspect and edit Three.js scenes, materials, shaders, lights in real time from any AI agent
About
Inspect and edit Three.js scenes, materials, shaders, lights in real time from any AI agent
What You'll Need
Set these up before or after installing:
Dev server port to proxy (auto-detected from package.json if not set)
Environment variable: DEV_PORT
Bridge proxy port (default: 9222)
Environment variable: BRIDGE_PORT
Set to 'none' to disable auto-opening browser
Environment variable: BROWSER
Set to 'true' for headless browser mode (CI)
Environment variable: HEADLESS
Custom Chrome/Edge executable path
Environment variable: CHROME_PATH
How to Install
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-dmitriygolub-threejs-devtools": {
"env": {
"BROWSER": "your-browser-here",
"DEV_PORT": "your-dev-port-here",
"HEADLESS": "your-headless-here",
"BRIDGE_PORT": "your-bridge-port-here",
"CHROME_PATH": "your-chrome-path-here"
},
"args": [
"-y",
"threejs-devtools-mcp"
],
"command": "npx"
}
}
}Security Report
4.8
Use Caution4.8High RiskA well-structured Three.js developer tools MCP server with proper functionality scoping. The code is clean with appropriate browser automation using puppeteer for legitimate development purposes. The extensive tool set is reasonable for debugging 3D graphics applications, and browser automation is necessary for the server's stated purpose of inspecting Three.js scenes. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 3 high severity). Package verification found 1 issue.
Scanned 4 files · 8 findings
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Required
This plugin requests these system permissions. Most are normal for its category.
Reviews
5.01 rating
51
40
30
20
10
No written reviews yet. Be the first!