Skip to main content
Glama
ODU33104

rive-mcp

by ODU33104
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to rive-mcp

No user-submitted related servers found.

    Related Servers

    • RiveMCP

      paradoxsyn
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to create and edit Rive animations through 139 MCP tools, supporting shapes, animations, state machines, physics, and export to .riv or .rev files.
      453 npm
      -

    • Spine Motion MCP

      nihatcagri44
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables authoring, preview, and export of Spine 2D skeletal animations via natural language from Claude Code or any MCP client, with a web dashboard and tools for keyframing, templates, and GIF preview.
      4
      MIT

    • Rive MCP Server

      astralisone
      F
      license
      Not graded
      quality
      F
      maintenance
      Orchestrates Rive animations by enabling discovery, integration, and composition across frameworks like React and Vue, with code generation and multi-backend storage.
      5
      -

    • mixamo-mcp

      V1xel
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude Code to automate Mixamo: browse/search animations, upload custom characters via Auto-Rigger, set animation parameters, and download animations with your character.
      2
      -
    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.8/5.0

    Scored across 30 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, and the descriptions explicitly disambiguate adjacent families like riv_visual_diff vs riv_ab_compare and riv_inspect vs riv_dump vs riv_decompile. The main risk is the large cluster of render/import/review tools, where an agent could momentarily pick the wrong one without reading the descriptions carefully.

    Naming Consistency4/5

    All tools share the riv_ prefix and snake_case, and most follow a verb-first pattern like riv_create, riv_render_frame, or riv_import_svg. However, several names are noun phrases or reverse the verb/object order, such as riv_asset_search, riv_lottie_import, riv_batch_render, riv_visual_diff, and riv_studio_notes, so the pattern is not fully uniform.

    Tool Count2/5

    At 30 tools, this is a heavy surface area and exceeds the 25+ threshold, especially when many tools belong to the same families. Several render tools could plausibly be unified behind a single format parameter, and the diff/compare/review cluster adds similar cognitive load.

    Completeness5/5

    The surface covers the full Rive production pipeline: discovery, inspection, creation, editing, optimization, decompilation, linting, critique, import from SVG/Lottie/icons, rendering to many formats, batch/CI workflows, rigging, asset extraction, code generation, and a live studio. There are no obvious dead ends, and the intended workflows are explicitly supported.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources