Skip to main content
Glama
Sign In
fakepose-mcp

fakepose-mcp

by hpdkhoa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to fakepose-mcp

No user-submitted related servers found.

    Related Servers

    • io.github.hpdkhoa/poselab-mcp

      hpdkhoa
      A
      license
      B
      quality
      B
      maintenance
      Enables models to pose and measure first-person arms and a rifle in Blender, reporting positions in named frames, clearances, visibility, screen placement, and solving rifle moves against goals.
      17
      58 PyPI
      1
      MIT

    • Kimodo MCP

      jon-jc
      A
      license
      B
      quality
      B
      maintenance
      Enables MCP clients such as Codex and Claude to plan natural-language or timed actions, generate and revise skeletal motion locally through a Kimodo runtime, and review results with diagnostics, candidate comparison, and interactive 3D previews. Provides checked handoffs of verified exports into Blender and Unreal Engine.
      37
      MIT

    • Cascadeur MCP

      MnxD2A6
      A
      license
      B
      quality
      B
      maintenance
      Enables MCP clients to inspect and edit animation inside a running Cascadeur instance without Computer Use, including scene/object and skeleton rig inspection, bounded joint and Point-target pose edits, snapshots, playback observation, and FBX export.
      4
      37
      2
      MIT

    • Weapon Lab

      hpdkhoa
      A
      license
      C
      quality
      B
      maintenance
      Enables AI clients to track first-person weapon bugs as measurable cases, run a game's own probe to gather metrics and screenshots, and compare candidate fixes against a baseline before a change is approved. It also reads posed weapon parts dumps, rebuilds animation clips in Blender, and validates probe contracts.
      67
      2
      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

    B3.4/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools are clearly distinct: list/show/set form an obvious preset CRUD subset, run_hands executes, and hold_report vs clip_report cleanly split hold vs clip diagnostics. Minor overlap exists because list_presets also surfaces captured grips while hold_report reports on holds, which could momentarily blur when to use which for grip data.

    Naming Consistency4/5

    All names use snake_case and are predictable. The verb_noun pattern holds for list_presets, show_preset, set_preset, and run_hands, but the two report tools use noun_report instead of a verb prefix, a minor deviation.

    Tool Count5/5

    Six tools is well-scoped for a focused Blender gun-kit hands pipeline: preset listing/inspection/authoring, one execution tool, and two complementary post-run reports. Every tool has a clear role with no filler.

    Completeness4/5

    The surface covers the main lifecycle: inspect presets, author/replace a hold, execute the hands step, and review hold and clip outcomes. The notable gap is a delete/remove operation for presets or captured grips, plus reports only reflect the last run, but these are workable around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources