Three.js DevTools MCP
NPM · THREEJS-DEVTOOLS-MCP · SCANNED SEP 23
Inspect and edit Three.js scenes, materials, shaders, lights in real time from any AI agent
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- A known CVE affects extract-zip, but no fixed version has been published, so there is nothing to upgrade to. View diagnostics → Partial
- No install/post-install scripts declared.Pass
- 50 of 170 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 183 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 4283 tokens (~83/item across 51 items; 51 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "run_js" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 51 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Three.js DevTools MCP server?
Three.js DevTools MCP runs locally as an npm package, launched with npx -y threejs-devtools-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · threejs-devtools-mcp
claude mcp add dmitriygolub-threejs-devtools -- npx -y threejs-devtools-mcp
{
"mcpServers": {
"dmitriygolub-threejs-devtools": {
"command": "npx",
"args": [
"-y",
"threejs-devtools-mcp"
]
}
}
} {
"servers": {
"dmitriygolub-threejs-devtools": {
"command": "npx",
"args": [
"-y",
"threejs-devtools-mcp"
]
}
}
} codex mcp add dmitriygolub-threejs-devtools -- npx -y threejs-devtools-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dmitriygolub-threejs-devtools": {
"type": "local",
"command": [
"npx",
"-y",
"threejs-devtools-mcp"
],
"enabled": true
}
}
} openclaw mcp add dmitriygolub-threejs-devtools --command npx --arg -y --arg threejs-devtools-mcp
mcp_servers:
dmitriygolub-threejs-devtools:
command: "npx"
args: ["-y", "threejs-devtools-mcp"] {
"McpServers": {
"dmitriygolub-threejs-devtools": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"threejs-devtools-mcp"
]
}
}
} assistant mcp add dmitriygolub-threejs-devtools -t stdio -c npx -a -y threejs-devtools-mcp
{
"mcpServers": {
"dmitriygolub-threejs-devtools": {
"command": "npx",
"args": [
"-y",
"threejs-devtools-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −3
- Stability: pass → 0.80 functional
- 17 Sept 26 +1
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 −3
- Stability: pass → 0.80 functional
- 10 Sept 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Sept 2026 · Analysed npm/threejs-devtools-mcp@0.2.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 2 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-7pqw-9j4j-h8q3 | CVE-2026-19693 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H | no |
| GHSA-jmr9-qjv8-65gv | CVE-2026-56876 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N | no |
Background: What a vulnerability scan can and cannot prove →
Dependencies 170 packages
| Packages resolved | 170 |
|---|---|
| Stale | 50 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
toggle_wireframe ~84
Toggle wireframe on all materials or a specific object. Runtime only — for visual debugging. Debug only — page reload will reset. No code changes needed.
| Name | Type | Req | Description |
|---|---|---|---|
| enabled | boolean | – | true=wireframe on, false=restore original, omit=toggle |
| name | string | – | Object name (omit for whole scene) |
| uuid | string | – | Object UUID |
No output schema declared.
No examples provided.
What is the Three.js DevTools MCP server?
Three.js DevTools MCP is listed in the public MCP registry as io.github.DmitriyGolub/threejs-devtools. Inspect and edit Three.js scenes, materials, shaders, lights in real time from any AI agent. This page covers its npm package (threejs-devtools-mcp).
Is the Three.js DevTools MCP server safe to use?
Three.js DevTools MCP scores 82 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 23 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Three.js DevTools MCP server expose?
Three.js DevTools MCP exposes 51 tools: scene_tree, object_details, material_list, material_details, shader_source, and 46 more. Their descriptions and schemas cost roughly 4,283 tokens of context every time the server is loaded.
Is the Three.js DevTools MCP server still maintained?
Three.js DevTools MCP is still listed as active in the MCP registry. We last reached this channel on 23 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Three.js DevTools MCP server under?
Three.js DevTools MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.