It may understand the current Houdini session, but not which asset or shot it belongs to, which input version is current, where the .hip file should be saved, or what downstream work depends on it. That context can also disappear between sessions.
I built KeystoneMCP to provide that missing production layer. It is a local MCP server aimed primarily at solo artists and small creative projects.
KeystoneMCP lets an AI assistant manage:
Project folder creation
Tasks, assets and shots
File locations and naming rules
Work, review, publication and delivery files
Current and approved versions
Dependencies and blocked tasks
Project context across sessions
It works alongside Houdini MCP tools rather than replacing them. The Houdini MCP operates inside Houdini, while KeystoneMCP provides the wider project state, exact paths, input versions and workflow guidance.
The goal is to let AI handle more of the repetitive project organization while the artist remains focused on the creative work.
KeystoneMCP is currently free to claim for eligible indie users and businesses earning under $150,000 USD annually. Anyone eligible who claims it during the launch period keeps that version permanently. A low-cost Indie tier will follow in roughly one month.
Download [bishopvfx.gumroad.com]