Skip to main content
Glama
DmitriyGolub

threejs-devtools-mcp

by DmitriyGolub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to threejs-devtools-mcp

No user-submitted related servers found.

    Related Servers

    • sceneview-mcp by sceneview

      sceneview-mcpofficial

      sceneview
      A
      license
      Not graded
      quality
      A
      maintenance
      28 tools for 3D and AR development — code generation, validation, model search (Sketchfab), and complete API reference. Android (Compose + Filament), iOS (SwiftUI + RealityKit), Web (Kotlin/JS + Filament.js). The only MCP server for 3D mobile development.
      1,323
      Apache 2.0

    • Brick Builder MCP App

      dend
      A
      license
      Not graded
      quality
      C
      maintenance
      A Three.js MCP server for designing 3D brick constructions, enabling AI or interactive placement of bricks through natural language and providing tools to manage and export scenes.
      24
      MIT

    • genart-mcp

      genart-dev
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for creating and manipulating generative art with p5.js, Three.js, GLSL, Canvas2D, and SVG, featuring workspace management, parameter control, and screenshot capture.
      45 npm
      MIT

    • blender-lab-mcp-client

      A-to-PC
      A
      license
      A
      quality
      C
      maintenance
      MCP server for Blender that connects to the official Blender Lab add-on, exposing 27 tools for scene manipulation, object editing, materials, rendering, and Python execution through the add-on's actual wire protocol.
      27
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 60 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of Three.js development—scene hierarchy, geometry, materials, animations, performance, etc. Even similar tools like set_camera and set_light areclearly differentiated by their noun. Overlap is minimal (e.g., object_details vs overlay_selected serve different contexts).

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., add_helper, set_camera, scene_tree). Verbs are imperative and nouns specify the target, making the pattern predictable across the entire set.

    Tool Count3/5

    With 60 tools, the surface is large but still scoped to Three.js devtools. However, many tools are runtime-only previews (set_* tools) and some debug helpers could be consolidated, making the count feel heavy for the core debugging purpose.

    Completeness5/5

    The tool set covers almost every common debugging and modification need: inspection of all objects, materials, textures, shaders, animations, performance, screenshots, export, and even gltf-to-r3f conversion. No obvious gaps for typical Three.js development workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources