Skip to main content
Glama
Sign In
virada-kit

virada-kit

by gloscherrybomb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to virada-kit

No user-submitted related servers found.

    Related Servers

    • texel-mcp

      Brunovncs
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to create, validate, review, patch, save, share, and preview Minecraft textures and skins by compiling JSON specs deterministically to PNG, with review sheets, art feedback, docs, examples, and workspace-safe file operations.
      14
      73 npm
      MIT

    • cad-3d-builder

      CheckSim
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents to turn natural-language descriptions and dimensional sketches into validated, watertight 3D-printable STL files by compiling build123d scripts, inspecting meshes, and rendering deterministic multiview previews.
      MIT

    • blender-iso-mcp

      fr4ncisx
      A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to procedurally design and render stylized 2:1 dimetric isometric game assets in Blender, including NPR cel-shaded scenes, modular tilesets, 8-angle avatar turnarounds, and mathematically exact subpixel collision diamonds, with turnkey engine manifests for Phaser, Godot 4, and retro web games.
      10
      Apache 2.0

    • visualspec

      utkarshx27
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to convert natural-language briefs into structured visual specs, deterministically render typography and layouts, and run constraint-aware visual QA and targeted repair for image generation.
      45 npm
      Apache 2.0
    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

    A3.5/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct step or resource in the kit workflow: spec reading, template fetch, asset add/list, validation, flat-sheet rendering, rider preview, reference comparison, export, and import. The potentially overlapping render_sheets vs preview_kit and preview_kit vs compare_to_reference are clearly separated by their descriptions (flat layout vs on-rider view vs side-by-side reference). No two tools appear to do the same thing.

    Naming Consistency5/5

    All ten tools follow a consistent verb_noun snake_case pattern (get_kit_spec, get_template, add_asset, list_assets, validate_kit, render_sheets, preview_kit, compare_to_reference, export_kit, import_kit). Verbs are used predictably and no convention mixing is present.

    Tool Count5/5

    Ten tools is well-scoped for a kit-design workflow, with each tool earning its place as a stage (spec, template, assets, validate, render, preview, compare, export, import). Nothing feels redundant or padded.

    Completeness4/5

    The workflow lifecycle is essentially complete: read spec, get template, manage assets, validate, render, preview, compare against reference, and round-trip via export/import. The only minor gap is asset lifecycle management (add/list exist but no remove or rename), which agents can work around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources