Houdini MCP Project Comparison: capoomgit/houdini-mcp vs healkeiser/fxhoudinimcp

Introduction

As the MCP (Model Context Protocol) standard gains traction, more and more DCC applications are adding AI assistant integrations. In the Houdini ecosystem, two major open-source MCP projects currently exist:

1. capoomgit/houdini-mcp — an early-stage project with a clean, minimal structure
2. healkeiser/fxhoudinimcp — a newer, more feature-complete implementation

This post compares the two across architecture design, feature coverage, installation experience, and extensibility to help you pick the right one for your workflow.

Overview Comparison

Architecture Comparison

houdini-mcp (capoomgit)

1

Claude Desktop  ──(stdio)──>  MCP Bridge Script  ──(TCP :9876)──>  Houdini Plugin

• Communication: The MCP Bridge Script talks to Claude via stdin/stdout and to Houdini via a custom TCP socket.
• Server side: A hand-rolled HoudiniMCPServer listening on localhost:9876.
• Inspired by: Adapted from blender-mcp.

fxhoudinimcp (healkeiser)

1

Claude Desktop / Cursor / Claude Code  ──(stdio/streamable-http)──>  FXHoudini MCP Server  ──(HTTP :8100)──>  Houdini hwebserver

• Communication: The MCP Server talks to AI clients via stdio or streamable-http, and talks to Houdini via HTTP/JSON.
• Server side: Uses Houdini’s built-in hwebserver directly — no custom server process needed.
• Thread safety: Uses hdefereval.executeInMainThreadWithResult() to ensure all hou.* API calls run on the main thread.

Architecture Analysis

Verdict: fxhoudinimcp’s architecture is more robust — it reuses Houdini’s native components, reducing the surface area for custom-code bugs.

Feature Coverage Comparison

houdini-mcp Feature Set

Provides basic Houdini control:

• Create and modify nodes
• Execute Python / HScript code
• Basic scene operations
• OPUS integration: Connects to the OPUS procedural furniture and environment asset library via RapidAPI (exclusive feature)

fxhoudinimcp Feature Set (19 categories, 168 tools)

Highlights:

• One-click workflows: Instant Pyro, RBD, FLIP, and Vellum simulation setup
• Full USD/LOPs support: 18 tools covering the USD pipeline
• Copernicus (COPs) support: Image processing node operations
• Scene context analysis: Error detection and Cook chain tracing

Installation and Configuration Comparison

houdini-mcp Installation Steps

1. Install uv (Python package manager)
2. Manually create the Houdini scripts directory and copy files
3. Run uv add "mcp[cli]" in the directory
4. Manually create a Shelf Tool
5. (Optional) Create a Houdini Package JSON for auto-loading
6. Configure claude_desktop_config.json

1
2
3
4
5
6
7
8

{
  "mcpServers": {
    "houdini": {
      "command": "uv",
      "args": ["run", "python", "C:/path/to/houdini_mcp_server.py"]
    }
  }
}

fxhoudinimcp Installation Steps

1. pip install fxhoudinimcp (or uv pip install fxhoudinimcp)
2. Copy the Package JSON to the Houdini packages directory
3. Configure the MCP client

1
2
3
4
5
6
7
8
9
10
11
12

{
  "mcpServers": {
    "fxhoudini": {
      "command": "python",
      "args": ["-m", "fxhoudinimcp"],
      "env": {
        "HOUDINI_HOST": "localhost",
        "HOUDINI_PORT": "8100"
      }
    }
  }
}

Claude Code support (one-liner):

1

claude mcp add --scope user fxhoudini -- python -m fxhoudinimcp

Installation Experience Comparison

Client Support Comparison

Exclusive Features

Exclusive to houdini-mcp

• OPUS integration: Access to the OPUS procedural asset library (furniture and environment assets) via RapidAPI. Requires a RapidAPI account and an active API subscription.

Exclusive to fxhoudinimcp

• One-click simulation workflows: Pyro / RBD / FLIP / Vellum setup in a single call
• Deep USD/LOPs support: 18 dedicated tools
• Copernicus image processing: COPs node operations
• Scene error analysis: Automatic Cook error detection and reporting
• Environment variable configuration: HOUDINI_HOST, HOUDINI_PORT, FXHOUDINIMCP_AUTOSTART, and more
• Dual transport mode: stdio + streamable-http

Recommendations by Use Case

Choose houdini-mcp (capoomgit) if you:

• Only need basic AI control of Houdini
• Are already using a uv-based workflow
• Specifically need OPUS procedural asset library integration
• Have a simple project scope and want to get started quickly

Choose fxhoudinimcp (healkeiser) if you:

• Need comprehensive Houdini coverage (SOPs, LOPs, DOPs, TOPs, COPs, etc.)
• Work with USD/LOPs pipelines
• Want one-click simulation workflows (Pyro / FLIP / Vellum / RBD)
• Prefer a standardized installation via a PyPI package
• Use Claude Code CLI as your primary AI tool
• Need guaranteed thread safety
• Value active maintenance and long-term project evolution

Conclusion

Overall recommendation: For most users, fxhoudinimcp is the better choice — broader feature coverage, a more robust architecture, and a smoother installation process. If you specifically need the OPUS procedural asset library integration, houdini-mcp is worth a look as a complementary tool.

References

• capoomgit/houdini-mcp
• healkeiser/fxhoudinimcp
• blender-mcp — the project that inspired houdini-mcp