Skip to main content
Glama
Sign In
Weapon Lab

Weapon Lab

by hpdkhoa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Weapon Lab

No user-submitted related servers found.

    Related Servers

    • io.github.hpdkhoa/poselab-mcp

      hpdkhoa
      A
      license
      B
      quality
      B
      maintenance
      Enables models to pose and measure first-person arms and a rifle in Blender, reporting positions in named frames, clearances, visibility, screen placement, and solving rifle moves against goals.
      17
      58 PyPI
      1
      MIT

    • Companion Animation Pipeline

      arabianguy08
      A
      license
      B
      quality
      A
      maintenance
      Enables AI clients to control background Blender jobs over stdio so they can inspect a 3D character or companion model, calibrate its anatomy and named bones, bake and export animation, and numerically verify the persisted GLB for playback review. Includes a CLI, models and workspaces that stay local unless explicitly shared.
      9
      MIT

    • Coating Lab

      hpdkhoa
      A
      license
      C
      quality
      C
      maintenance
      Enables game gun models to be given physically based surface finishes across material slots and wear levels, with wear baked once into vertex-colour masks for edges, handling, rubbing parts and dirt. It also validates finishes and wear against physical rules, renders look-dev variant sheets, and exports per-slot engine material parameters.
      13
      30 PyPI
      1
      MIT

    • feellab-mcp

      hpdkhoa
      A
      license
      C
      quality
      B
      maintenance
      Enables measuring an FPS game's feel by judging probe-written timelines against an 82-item checklist covering latency, sync, kick, shake, presence, rhythm and smoothness, and returning per-item values, verdicts, Markdown reports or gate rows. It works with any engine that can emit the timeline contract, without running the game itself.
      6
      30 PyPI
      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

    C2.3/5.0

    Scored across 67 tools

    Disambiguation4/5

    The toolset is divided into clear functional prefixes (blueprint_, gunkit_, gate_, rig_, motion_, spec_, probe_), and within most groups each tool targets a distinct step or resource. A few near-pairs (gunkit_actions vs gunkit_action, gate_cases vs gate_evals, gunkit_rig vs blueprint_to_gunkit) could be misselected, but descriptions generally disambiguate them.

    Naming Consistency4/5

    Nearly all tools follow a predictable snake_case prefix_noun pattern (blueprint_scan, gunkit_rig, gate_run, motion_roll), grouped logically by pipeline stage. A couple of outliers (project_info, contract_check) break the prefix scheme, but overall naming is highly consistent.

    Tool Count2/5

    67 tools is a heavy surface for a single server, with 25 blueprint_* tools alone, which risks overwhelming an agent despite the pipeline's complexity. The scope is real but the count is well beyond a comfortably navigable set.

    Completeness4/5

    The surface covers a full weapon-development lifecycle: source ingestion, blueprint authoring, rigging, animation, gating/baselining, and export. Coverage appears broad with few obvious dead ends, though minor gaps in areas like proposal rejection/rework may exist.

    Resources