Skip to main content
Glama
KumarManuSaraswat

VoxelFlow Studio

by KumarManuSaraswat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to VoxelFlow Studio

No user-submitted related servers found.

    Related Servers

    • Blockbench MCP

      achmadawdi
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to control Blockbench for Minecraft 3D modeling, including project creation, cube placement, UV layout, and texture painting.
      GPL 3.0

    • BlockbenchMCP

      rastaralspi
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects Claude AI to Blockbench through the Model Context Protocol, enabling AI-assisted 3D modeling, texture creation, and block model manipulation. It supports creating, modifying, and deleting models, applying textures and materials, and tracking commands in real time.
      MIT

    • blockbench-mcp

      Mishaadevv
      A
      license
      B
      quality
      C
      maintenance
      Enables an AI agent to fully drive Blockbench through 69 tools covering 3D modeling, seeded procedural textures, UV mapping, animation, export codecs, files, and plugin management, plus arbitrary JavaScript inside the app when the built-in tools fall short. It bridges agent and editor over a token-gated localhost connection so models can be built, rendered, reviewed, and exported end to end with zero dependencies.
      72
      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 14 tools

    Disambiguation4/5

    Most tools have clearly distinct targets: get_editor_status/inspect_project are reads, create_model vs create_prop split humanoid vs prop, generate_rig/generate_animations/preview_animation are separated, and validate_asset/export_asset are distinct lifecycle stages. The main overlap is apply_materials (recolor the atlas) vs apply_prop_materials (change named colors on a prop), which an agent could easily misselect since both sound like material editing on VoxelFlow assets.

    Naming Consistency5/5

    All 14 tools follow a consistent snake_case verb_noun pattern (get_editor_status, create_model, generate_rig, validate_asset, cancel_operation, etc.). There are no mixed conventions or vague standalone verbs; apply_materials is slightly less specific in its noun but still fits the pattern.

    Tool Count5/5

    14 tools is well within the ideal range and each tool maps to a real step in the asset pipeline: inspect, create, material edit, rig, animate, preview, validate, export, undo, plus operation polling/cancel. Nothing appears redundant beyond the apply_materials pair.

    Completeness4/5

    The surface covers a full lifecycle: read state, create model/prop, edit materials, rig, animate, preview, validate, export, undo, and async operation handling. Minor gaps exist — there is no tool to list pending operations (only get_operation by known request_id) and no way to edit or add geometry after creation beyond materials/undo, but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources