Houdini toolkit plugin for Claude Code, Codex, and Antigravity (CLI & IDE). Bundles four skills plus a lightweight MCP server for inspecting .bgeo.sc caches and USD scene files without loading geometry.
| Skill | Purpose |
|---|---|
houdini-cli |
Drive Houdini's command-line tools (ginfo, gconvert, hrender, husk, usdrecord, hython, …) for geometry analysis, format conversion, and batch rendering. Detailed per-tool references live under skills/houdini-cli/references/. |
houdini-env |
Houdini environment variables, houdini.env syntax, and JSON package configuration. Covers HOUDINI_PATH, HOUDINI_DSO_PATH, HOUDINI_USER_PREF_DIR, package scan order, expression grammar, and best practices. |
houdini-locator |
Detect every Houdini installation on Windows or Linux and return the full path to hython / houdinifx for direct execution. |
houdini-lite |
Companion guide for the bundled MCP server: bgeo header / metadata / attribute inspection, frame-sequence scans, USD hierarchy and composition arcs, camera reads, prim-attribute queries, and Value Clip stitching. |
| Server | Purpose |
|---|---|
houdini-lite |
Reads .bgeo.sc files directly via Blosc decompression and BJSON parsing — no Houdini installation required. Inspects USD stages via a bundled pxr. |
See mcp-server-houdini-lite/README.md for the full tool reference (inputs, outputs, JSON examples).
- Python 3.11+
- uv — used by the bundled MCP server.
- A Houdini installation is not required for
houdini-lite. It is required forhoudini-cli(which drives real Houdini binaries) and is auto-detected byhoudini-locator.
Clone the repo anywhere convenient, then point your AI agent CLI at it. Paths below assume the clone lives at <repo-root> (e.g. ~/houdini-tools or C:\dev\houdini-tools).
git clone https://github.com/chordee/houdini-tools.gitThe MCP server pulls its own Python dependencies on first run via uv — no manual uv sync required.
Add the repo's parent directory as a marketplace in ~/.gemini/config/config.json (or ~/.gemini/settings.json), then enable the plugin:
"extraKnownMarketplaces": {
"houdini-tools": {
"source": {
"source": "directory",
"path": "<parent-of-repo-root>"
}
}
},
"enabledPlugins": {
"houdini-tools@houdini-tools": true
}Reload plugins (or restart your session) — the staged plugin and its MCP servers will load automatically.
Add the repo's parent directory as a marketplace in ~/.claude/settings.json, then enable the plugin:
"extraKnownMarketplaces": {
"houdini-tools": {
"source": {
"source": "directory",
"path": "<parent-of-repo-root>"
}
}
},
"enabledPlugins": {
"houdini-tools@houdini-tools": true
}Or use the /plugin UI inside Claude Code to add a local-directory marketplace pointing at the parent directory. Reload with /reload-plugins (or restart Claude Code) — houdini-lite MCP server starts automatically.
Register the repo as a Codex marketplace and enable the plugin:
codex plugin marketplace add "<repo-root>"# ~/.codex/config.toml
[plugins."houdini-tools@houdini-tools"]
enabled = trueCodex reads .mcp.json to launch the bundled MCP server.
| File | Purpose |
|---|---|
.claude-plugin/plugin.json |
Claude Code plugin manifest |
.codex-plugin/plugin.json |
Codex plugin manifest |
.mcp.json |
Codex MCP server configuration |
plugin.json |
Antigravity plugin manifest |
mcp_config.json |
Antigravity MCP server configuration |
houdini-tools/
├── .claude-plugin/plugin.json # Claude Code plugin manifest (with MCP server)
├── .codex-plugin/plugin.json # Codex plugin manifest
├── .mcp.json # Codex MCP server config
├── plugin.json # Antigravity plugin manifest
├── mcp_config.json # Antigravity MCP server config (with MCP server)
├── mcp-server-houdini-lite/ # Bundled MCP server (uv project)
└── skills/
├── houdini-cli/ # CLI tool reference + workflows
│ └── references/ # Per-tool deep dives (husk, usdrecord, …)
├── houdini-env/ # Environment variables & package configuration
├── houdini-locator/ # Houdini install detection scripts
└── houdini-lite/ # MCP tool usage guide