Skip to main content
Glama
hx-multianim-mcp

hx-multianim-mcp

by bh213

Related Servers

Alternatives to hx-multianim-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Connects an MCP client to a running Serious Editor 2017 / Serious Sam Fusion instance through a local Lua bridge, enabling package and entry inspection, log reading, editor diagnostics, and previewed/undoable entity property edits on a captured selection.
      14
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      Connects MCP clients to a local browser-based map editor, enabling session discovery, map state inspection, item and actor queries, actor placement and movement, selection changes, deletion, and undo/redo operations. Supports STDIO, Streamable HTTP, and legacy HTTP+SSE transports through a local WebSocket bridge.
      10
      MIT
    • A
      license
      D
      quality
      C
      maintenance
      Enables AI clients to control and inspect a Unity Editor through MCP tools for scene and play-mode operations, logs, screenshots, assertions, Lua execution, UI interaction, world observation, and bridge management; advanced UI/Lua/world features require project-specific adapters.
      41
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables an MCP client to connect to a running Blockland client to execute TorqueScript, inspect player state, control character movement and actions, and capture screenshots.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Connects MCP clients directly to a live Godot editor, enabling AI assistants to build scenes, edit nodes, and control the editor through over 120 operations.
      47
      20,833 PyPI
      3,409
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      This MCP server drives Defold games through an in-game debug bridge, allowing MCP clients to build, launch, playtest, and interact with real game builds via tools for input, screen reading, state, and logs.
      9
      1
      MIT

    TDQS

    A3.6/5.0

    Scored across 38 tools

    Disambiguation4/5

    Most tools target a clearly distinct subsystem (scene graph, interactives, traces, events, tweens), but a few clusters overlap: get_parameters vs inspect_programmable vs list_active_programmables all surface parameter values, and list_resources vs list_fonts vs list_atlases are superset/subset. send_event vs send_events vs click_button also need the descriptions to disambiguate. Boundaries are mostly clear thanks to detailed descriptions.

    Naming Consistency4/5

    Names overwhelmingly follow snake_case verb_noun or verb patterns (list_*, get_*, set_*, inspect_*, send_event(s)), with no camelCase mixing. Minor deviations like single-word verbs (connect, ping, quit, pause, step, reload, screenshot) and coordinate_transform are still readable and consistent in spirit.

    Tool Count3/5

    38 tools is heavy, well past the 3-15 sweet spot. The domain is genuinely broad (input, inspection, resources, screens, programmables, diagnostics, events), so most tools map to a distinct subsystem rather than being redundant, but the surface is still on the bulky side.

    Completeness5/5

    Covers the full debug-bridge lifecycle: connect/quit, pause/step, input injection, hot-reload, eval, screenshot, scene/element/programmable inspection, resource and screen listing, plus diagnostics (traces, errors, debugger hits, performance) and game-specific ops/events. No obvious dead ends for the stated purpose.