Houdini 22 brings MCP agents into character rigging workflows

SideFX released Houdini 22 in July with a preview of MCP-powered AI agents built into the KineFX character rigging toolset. The integration generates and explains Apex Script code for rig construction while the artist reviews and controls every output. It's not a black box; it's code you can read, edit, and iterate on.

For character animation teams, the friction point has always been rig scaffolding. Procedural workflows reduce manual setup time, but writing and maintaining Apex Script demands specialists. MCP agents lower that barrier. A rigger can describe a rig behavior in natural language, let the agent draft the code, then refine it in context. The artist stays in the driver's seat.

What actually changed

Houdini 22 rolled in three major moves for simulation and character work. The KineFX updates are procedural-first, which means faster iteration and easier collaboration between riggers and animators sharing the same rig graph. Copernicus, the image-processing framework, gained new tools for character animation and USD world building. And SideFX added a full Gaussian splatting toolkit, so training splats from reference photos or generating them from 3D scenes stays in-house rather than bouncing to a separate tool.

The MCP agents are marked as preview, not production-ready yet. SideFX is being careful with how it ships AI into the pipeline, which reads as respect for the artists who need to trust the code they're running.

Why procedural rigging matters now

Artists working on character-heavy projects have been sideloading procedural logic into Houdini for years. Teams at larger studios built custom tools to automate rig setup. SideFX is now making that pattern built-in, with AI assistance taking on the boilerplate. For animation shops handling character work at scale, that cuts iteration cycles. You're not waiting for a specialist to rewrite rig logic; you're teaching the agent the pattern once and applying it across variants.

Vision For Xperiences has run character rigs through Houdini procedurally for product and cinematic work. The bottleneck is usually not the rig itself, but the setup labor and communication overhead between modeling, rigging, and animation departments. Procedural workflows with agent-assisted code generation compress that gap.

The splatting layer

The bundled Gaussian splatting toolkit is worth noting because it keeps the entire pipeline inside Houdini. Train splats, animate them with standard deformation nodes, relight them to match their environment, render them with Karma. For work involving photogrammetry or reference-based 3D capture, that's one fewer tool handoff. You can test splatting as a supplementary layer for assets where raster geometry is overkill.

Vision For Xperiences has explored splats for VFX set extensions and environment work where training time and render cost matter. Native Houdini integration removes the friction of jumping to a separate splat application, running training, exporting, and re-importing.

The waiting game

AI in creative tools has a trust tax. Riggers need to understand what the agent produced before shipping it. SideFX positioned MCP as a preview feature, not a finished product, which is the right move. The early adopters will spot edge cases and limitations. By the time it's stable, there will be a clear set of workflows where it saves time without introducing hidden failure modes.

For teams considering an upgrade, the procedural KineFX updates and the splatting toolkit are solid on their own. The MCP agents are a bonus layer to experiment with if your pipeline has room for it.

Quick answers

Do I need to retrain my team to use MCP rigging agents?

Not heavily. Riggers still write rig logic in Apex Script; the agent just scaffolds the code faster. The artist reviews and edits every line. If your team already uses procedural rigging in Houdini, MCP accelerates what you're already doing.

Can I export splats from Houdini 22 to other renderers?

SideFX's toolset is optimized for Karma, Houdini's native renderer. For external renderers, you'd export splat geometry or point clouds and rely on third-party splat plugins. The native integration is a strength if you render in-house.

Is Houdini 22 backward compatible with older rigs?

Yes. KineFX enhancements are additive. Existing character rigs continue to work. The procedural and AI features are new patterns you adopt when starting fresh builds or refactoring legacy setups.

Referenced

Image: “EhrichWeissHoudini1890” by Unknown authorUnknown author, via source. Licensed Public domain.