Vi3W
Skip to content

Guides

Retargeting Mixamo-style animations with an AI agent: what Claude can automate in Blender

Use Claude and Blender MCP to retarget Mixamo animations: bone mapping, constraints, baking, Rigify targets and the cases an agent still gets wrong.

6 min read

A translucent toy robot mid-stride with a glowing skeleton rig visible inside and ghosted earlier poses trailing behind
Illustration. Retargeting copies motion from one skeleton onto another.

Quick answer

Can an AI agent retarget Mixamo animations?

Moving a motion clip from one skeleton to a differently named or proportioned one is a mapping job, and an agent connected to Blender over MCP is good at mapping. Claude can read both armatures, pair bones by name, add Copy Rotation constraints, bake the result and report bones it could not match.

What retargeting actually is

You have a motion clip made for one skeleton and a character with a different one. Retargeting copies the motion across: the walk that was keyed on mixamorig:LeftArm has to end up on your character's upper_arm.L, at the right angle, without the arms passing through the chest.

Three things make it hard:

  • Names differ. Mixamo prefixes every bone with mixamorig:. Rigify, Auto-Rig Pro, game-engine skeletons and AI riggers each use their own naming.
  • Rest poses differ. Mixamo characters rest in a T-pose. Many custom rigs rest in an A-pose. Copying rotations between different rest poses tilts the arms.
  • Proportions differ. A long-legged clip on a short character slides the feet, because the hips move the same distance on shorter legs.

None of these needs creativity. They need a careful, boring mapping, which is the kind of work an AI agent does well when it can see both skeletons.

Why an agent helps here

The tedious part of retargeting in Blender is the bone-by-bone setup: 50-odd bones, two constraints each, then a bake. With Blender connected to Claude over MCP, the agent can read the armatures directly instead of guessing from your description. Setup for that connection is in Blender MCP with Claude.

What the agent brings:

  • It reads every bone name in both armatures and pairs them, including fuzzy matches like LeftForeArm to forearm.L.
  • It writes and runs the constraint script, then bakes.
  • It tells you which bones it could not pair, so the gaps aren't silent.

What it does not bring is judgement about how the motion looks. You still scrub the timeline.

The workflow, step by step

1. Prepare both files

  • Download the clip from Mixamo as FBX. Use Without Skin if you only need the motion.
  • Import both into one Blender scene: File ‣ Import ‣ FBX for the clip, and your character in whatever format you have.
  • Apply scale on both armatures (Ctrl+A ‣ Scale). Mixamo FBX files often come in at 100× or 0.01× scale, and a mismatch breaks location constraints.
  • Match the rest pose if you can. If your character is in an A-pose, either pose it into a T-pose and apply that as the new rest pose, or accept a fixed arm offset that you correct later.
  • Save the file. The agent runs Python inside Blender, and you want an undo point outside it.

2. Ask the agent to map the bones

A prompt that works:

"There are two armatures in the scene: Armature_Mixamo (source) and Armature_Hero (target). List every bone in each. Build a mapping from source to target by name and anatomy, strip the mixamorig: prefix, and show me the mapping as a list before changing anything. Mark any target bone with no match."

Ask for the list first. It's your chance to catch wrong pairings, such as a spine bone mapped to a neck bone, before anything is constrained.

3. Constrain and bake

Once the mapping looks right:

"For each pair, add a Copy Rotation constraint on the target bone pointing at the source bone, in world space. On the hips, also add Copy Location. Then bake the action on Armature_Hero for the clip's frame range with Visual Keying on and Clear Constraints on, and name the action Hero_Walk."

Blender's Object ‣ Animation ‣ Bake Action (Blender manual on armatures covers the skinning side) (Pose Mode: Pose ‣ Animation ‣ Bake Action) turns constraint-driven motion into real keyframes. With Clear Constraints ticked, the target armature is left with plain keys you can edit.

4. Review in the viewport

Scrub the timeline, and watch for these:

  • Arms through the body: the rest-pose mismatch. Add a rotation offset on the upper arms, or fix the rest pose and re-bake.
  • Foot sliding: proportion mismatch. Scale the hip location constraint's influence, or scale the source armature to the target's leg length before baking.
  • Twisted forearms: an axis mismatch between rigs. Ask the agent to try Copy Rotation in local space with the mix mode changed for those bones only.

5. Clean up

Delete the source armature and its mesh, keep the baked action, and push it to an NLA strip if you want to stack several clips. Export as FBX with Bake Animation on, or GLB for web and engines.

A wooden mannequin in four key poses along a glowing timeline
Illustration. After baking, every frame is a real keyframe you can edit.

Retargeting onto Rigify

Rigify separates deform bones (DEF-) from control bones. If you constrain the deform bones, the controls fight them. Target the FK controls (upper_arm_fk.L, forearm_fk.L, thigh_fk.L, shin_fk.L) and the torso control for the hips, set the limbs' IK/FK switch to FK, then bake onto the control rig. Tell the agent this explicitly. Without it, most agents go for the bone names that look closest, which are the DEF- ones.

Retargeting in game engines instead

If the clip is going into an engine anyway, the engine's own retargeting may be simpler than Blender:

  • Unity: set both models' rigs to Humanoid in the import settings, and humanoid clips play on any humanoid avatar.
  • Unreal Engine 5: an IK Retargeter asset maps one skeleton's chains to another's.
  • Godot 4: a bone map against the humanoid skeleton profile on import.

An agent can still help there by writing the bone map or checking that the names match, but the solving happens in the engine. For export settings, see AI 3D models for Unity and for Unreal Engine.

What an agent can't do

  • It can't see motion quality. It can read keyframe values and take a viewport screenshot, but a still frame doesn't show foot sliding. You watch the playback.
  • It won't fix a bad rig. If your character's weights are wrong, retargeted motion exposes it. Fix the skinning first: Blender rig not moving the mesh.
  • It doesn't make Mixamo rig non-humans. Adobe states the auto-rigger and animation library are for bipedal humanoids. A dog won't take a Mixamo walk however well the bones are mapped.
  • It gets long scripts wrong. Ask for one stage at a time (list, map, constrain, bake), not "retarget everything" in one go.

When you don't have a rigged character yet

If your character is a fresh AI mesh with no skeleton, retargeting is the second problem, not the first. In Vi3W, Add bones rigs a generated humanoid (or an animal, with It's an animal), and Make it move applies preset moves (Idle, Walk, Run, Jump, Wave, Dance) or a described motion matched from a clip library. Download it as FBX or GLB, and retarget extra clips onto that skeleton in Blender with the workflow above. From a chat, the same tools are available through Vi3W's MCP server: see rig and animate from chat with the Vi3W MCP. For a clean mesh before rigging, see can Claude retopologize a mesh?.

Rig and animate a model in Vi3W

Frequently asked questions

how to retarget mixamo animation in blender

Import the Mixamo FBX and your character, then constrain each bone of your character's armature to the matching Mixamo bone (Copy Rotation for limbs, Copy Location as well for the hips), bake the action with Object ‣ Animation ‣ Bake Action and remove the constraints. An agent over Blender MCP can do the bone pairing and constraint setup for you.

retarget mixamo to rigify

Rigify is controlled through control bones, not deform bones, so target the FK controls (for example upper_arm_fk.L) rather than the DEF bones, and switch the limbs to FK before baking. Give the agent a mapping table for the controls and ask it to stop if a control is missing.

is mixamo free for commercial use

Adobe says Mixamo is free with an Adobe ID, with no Creative Cloud subscription needed, and that its characters and animations are royalty-free for personal and commercial projects. Check Adobe's current terms before shipping.

Last reviewed