Skip to main content
Glama
NevelStudios

roblox-vfx-lab

by NevelStudios
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to roblox-vfx-lab

No user-submitted related servers found.

    Related Servers

    • blender-fx-mcp

      choisam4u-creator
      A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to create Blender FX such as destruction, explosions, water, fire, particles, wind, ocean, and cloth from natural language instructions, including physics simulation and preview rendering.
      32
      MIT

    • Roblox Studio MCP

      EL4CTEO
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to inspect, create, edit, debug, and playtest projects inside the Roblox editor via 29 lean tools, with push-based SSE transport, editor-safe script edits, and batched undoable writes.
      35
      483 npm
      11
      MIT

    • Material Maker MCP

      graysonchalmers
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to create Material Maker node graphs from natural language, validate them against the node catalog, and render them headlessly to PBR texture maps and editable .ptex files.
      9
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.9/5.0

    Scored across 12 tools

    Disambiguation4/5

    The tools mostly target distinct stages of the VFX pipeline: node CRUD, GPU render, final bake, upload, Studio apply, Studio capture, and local viewer. The closest overlaps are vfx_render vs vfx_bake and vfx_preview vs vfx_viewer, but the descriptions make the boundaries clear.

    Naming Consistency4/5

    All tool names use lower snake_case with a consistent vfx_ prefix, which makes the set readable. There are minor deviations: the shader CRUD tools use a shader_ infix while vfx_delete is generic, and vfx_viewer/vfx_guide are noun-like rather than verb-like.

    Tool Count5/5

    Twelve tools is well within the ideal range and each one maps to a distinct step in the workflow. Nothing appears redundant or padded.

    Completeness4/5

    The surface covers the full node lifecycle (list/read/write/edit/delete) plus rendering, baking, uploading, applying, previewing, viewing, and guidance. A minor gap is the lack of explicit bake listing/reading tools, though bakes can be inspected through the viewer or filesystem.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources