Skip to main content
Glama
toolbox-design-ia

hiero-mcp

by toolbox-design-ia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to hiero-mcp

No user-submitted related servers found.

    Related Servers

    • nuke-mcp

      joshw051
      A
      license
      B
      quality
      D
      maintenance
      A production-grade MCP server for Foundry Nuke that enables AI assistants to understand and manipulate compositing environments, including AOVs, deep workflows, distortion, tracking, OCIO/ACEScct, and CopyCat ML.
      45
      MIT

    • Podcast MCP

      calebn
      A
      license
      C
      quality
      A
      maintenance
      Enables podcast producers and agents to manage multitrack projects, run per-track transcription, perform transcript-driven edits, process audio via FFmpeg, and inspect a read-only DAW timeline over MCP.
      183
      MIT

    • kitsu-mcp

      EstienneG
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables users to query and manage Kitsu/Zou production data, including projects, shots, assets, tasks, people, previews, video review, and optional write actions, through an MCP interface. Supports local stdio use and hosted HTTP connectors with per-user Kitsu authentication and read-only defaults.
      MIT

    • houdini

      JUSTDOITzhw
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables language models to inspect the current Houdini scene, create and modify nodes, and run VEX/Python code in the running Houdini session via MCP.
      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.9/5.0

    Scored across 45 tools

    Disambiguation4/5

    Most tools map to distinct resource/action pairs across projects, bins, clips, sequences, tracks, shots, tags, selection and viewer. A few close pairs exist (get_clip vs get_track_item, update_sequence vs update_track_item, the various list_* tools), but descriptions make the boundaries mostly clear. execute_python is an explicit catch-all and does not substantially muddy the dedicated tools.

    Naming Consistency4/5

    The set is predominantly consistent snake_case verb_noun naming (list_projects, create_sequence, update_track_item, add_tag). Minor deviations include new_project instead of create_project, and standalone verbs such as undo, redo and razor. These are readable and predictable overall.

    Tool Count2/5

    With 45 tools this is a very heavy surface for a single MCP server, even for a complex DCC integration. Many list/get variants and separate tag, selection, viewer and effect tools make the set harder to navigate than necessary. Some consolidation would improve usability.

    Completeness3/5

    Core lifecycle coverage is strong for projects, bins, clips, sequences, tracks and track items, and export/tag/selection/viewer basics are present. Notable gaps remain around effects (add only, no update/delete/list), export job status/cancellation, and project settings editing. execute_python can work around these gaps, but they are still visible omissions.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources