Skip to main content
Glama
bluemoonfoundry

vangard-daz-mcp

by bluemoonfoundry
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to vangard-daz-mcp

No user-submitted related servers found.

    Related Servers

    • Daz Pilot

      millsydotdev
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for AI-driven DAZ Studio scene editing. Runs as a native DAZ Studio plugin (DLL) and exposes all scene control, rendering, dForce, asset, and animation commands through the Model Context Protocol.
      7
      MIT

    • unreal-mcp-server

      Jeanosasco
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that connects Claude to Unreal Engine 5.8 via the official Remote Control API, enabling asset manipulation, actor control, level operations, and AI-powered 3D model generation (via Meshy) through natural language.
      -

    • blender-mcp

      sandraschi
      A
      license
      C
      quality
      A
      maintenance
      Enables AI-powered control of Blender through natural language, allowing users to create, manipulate, and automate 3D scenes, objects, materials, animations, and more via Claude or other MCP clients.
      71
      44
      MIT

    • orcaslicer-mcp

      MaxEllis
      A
      license
      A
      quality
      A
      maintenance
      MCP server that lets Claude drive a real, running OrcaSlicer: load models, arrange the plate, tune settings, slice, and read results back.
      44
      45
      AGPL 3.0

    • resolve-mcp

      danielbaldwin47
      F
      license
      A
      quality
      B
      maintenance
      An MCP server that gives Claude Code hands inside DaVinci Resolve Studio, enabling project management, status checks, snapshots, and arbitrary Python scripting via the Resolve API.
      5
      1
      -
    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.1/5.0

    Scored across 70 tools

    Disambiguation4/5

    Most tools have distinct purposes, but some camera and framing tools (e.g., daz_frame_camera_to_node vs daz_frame_shot) overlap slightly. Descriptions are detailed enough to differentiate, though agents might occasionally misselect.

    Naming Consistency5/5

    All tools follow the 'daz_verb_noun' pattern consistently, including async variants (e.g., daz_render_async, daz_batch_render_cameras_async). Even utility tools like daz_status fit the pattern. No mixing of conventions.

    Tool Count3/5

    70 tools is on the higher end for a single server, covering a broad domain. While each tool serves a specific need, some could be consolidated (e.g., multiple framing tools). Still, the count is reasonable given DAZ Studio's complexity.

    Completeness4/5

    Covers scene management, cameras, lighting, rendering, animation, morphs, posing, and content browsing. Minor gaps exist (e.g., no dedicated material or geometry creation tool), but the daz_execute tool allows arbitrary scripting to fill missing functionality.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources