threejs-editor-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| THREEJS_EDITOR_PROJECT_ROOT | No | The absolute path to the root directory for Three.js projects. Can also be provided via the --root command line argument. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsA | Lists projects available in the configured Three.js project root. |
| create_projectB | Creates an empty or Pong Three.js project and opens its editor. |
| open_editorA | Opens the editor for an existing Three.js project. |
| inspect_projectB | Reads the current scene, script, diagnostics, and recent human edit operations. |
| apply_scene_changesB | Applies one revision-checked batch of bounded scene, script, or project changes. |
| check_projectC | Checks scene and camera loading, script syntax, and diagnostics for the current revision. |
| pull_projectC | Returns the project when the editor revision is stale. |
| push_projectC | Saves one editor snapshot when its base revision is current. |
| save_project_copyC | Persists the editor snapshot under a new project ID. |
| report_diagnosticsC | Records Play errors and warnings for one exact project revision. |
| put_assetB | Stores one bounded GLB, PNG, or JPEG asset for the current project revision. |
| export_projectB | Returns a bounded JSON export containing the saved project and original assets. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| threejs-editor-view |
TDQS
Scored across 12 tools
Most tools have clearly distinct purposes, but inspect_project and check_project both report diagnostics, and create_project also opens the editor, creating slight overlap. Descriptions generally help agents choose correctly.
All tool names follow a consistent verb_noun snake_case pattern (e.g., open_editor, list_projects, apply_scene_changes), making the API predictable and easy to navigate.
With 12 tools, the server is well-scoped for a Three.js project editor, covering project lifecycle, scene manipulation, and diagnostics without unnecessary bloat.
Core workflows such as create, open, inspect, modify, save, and export are covered, but missing operations like delete_project or asset retrieval leave minor gaps in full lifecycle management.