@graphty/babylonjs-inspector-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GEMINI_API_KEY | No | Gemini API key. When unset, the babylonjs_scene_analyze tool is not registered. | |
| BABYLONJS_INSPECTOR_HOST | No | Interface the server binds to. Loopback by default so the bridge is not reachable from other machines. Must be non-empty. | 127.0.0.1 |
| BABYLONJS_INSPECTOR_PORT | No | Port for the HTTP + WebSocket server. Must be 1-65535 or startup fails with an explicit error. | 9070 |
| BABYLONJS_INSPECTOR_LOG_LEVEL | No | One of debug, info, warn, error. Validated at startup, but no logger reads it yet. | info |
| BABYLONJS_INSPECTOR_SCREENSHOT_DIR | No | Directory for screenshot output. Read with a default applied, but not validated and not yet consumed by any code path. | ./tmp/screenshots |
| BABYLONJS_INSPECTOR_ALLOWED_ORIGINS | No | Comma-separated list of extra browser origins allowed to open a WebSocket. Loopback origins are always allowed. '*' disables the check. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| babylonjs_connection_statusA | Check the current connection state of the BabylonJS inspector. Returns whether a browser is connected, the engine type, rendering capabilities, and which tool categories are available. |
| babylonjs_scene_inspectA | Inspect the BabylonJS scene. Use 'summary' for an overview, 'full' for complete scene graph, or drill into specific categories: meshes, mesh_detail, materials, material_detail, cameras, lights, animations, textures, physics, post_processing, performance, scene_tree, webgl_errors. Use 'target' for specific items and 'filter' for glob-based name filtering. |
| babylonjs_scene_evaluateA | Execute a JavaScript function against the BabylonJS scene. The function receives (scene, engine, BABYLON) as arguments. Return values are serialized to JSON. Use this for custom queries or operations not covered by other tools. |
| babylonjs_screenshotA | Capture one or more screenshots of the BabylonJS scene. Supports multiple preset camera angles, depth maps, and custom camera positions. Screenshots are saved to the tmp/ directory and file paths are returned. Only available when a browser with rendering is connected. |
| babylonjs_spector_captureA | Capture a WebGL frame using Spector.js for low-level rendering inspection. Returns draw call count, shader source code, WebGL state, texture bindings, and performance data. Only available when a browser with WebGL is connected. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinct primary purpose: status, inspection, evaluation, screenshots, and WebGL capture. scene_inspect and scene_evaluate have some potential overlap since both query the scene, but the descriptions clearly separate structured inspection from custom JavaScript execution.
All tools share the babylonjs_ prefix, and most follow a scene/domain + action pattern, such as scene_inspect and scene_evaluate. However, babylonjs_screenshot and babylonjs_connection_status break the verb-noun pattern slightly, making the naming mostly but not fully consistent.
Five tools is a well-scoped set for an inspector-focused MCP server. Each tool covers a major capability area without unnecessary redundancy, and the count feels appropriate for the server's purpose.
The tool surface covers connection status, scene inspection, custom evaluation, screenshots, and low-level WebGL capture, which covers the core inspection workflow. Direct mutation tools are absent, but babylonjs_scene_evaluate provides a flexible escape hatch, so major workflows are not blocked.