Product

Integrations

Hydrilla AI connects to the tools you already run: a Blender add-on, plugins for Unity, Unreal, and Godot, a local Bridge from Studio, and MCP and REST for custom pipelines.

Generation is most useful when it happens next to the work. Each integration below brings Hydrilla into a tool your team already knows, so artists can generate, receive, and place models without leaving their scene, and engineers can wire generation into the systems around it.

From Studio to your open scene

The local Bridge runs on your machine and sends meshes from Studio into Blender, Unity, Unreal, or Godot. Start it from a plugin, then use Send to DCC in Studio. The model arrives in the tool you have open, so you can review it in context, under your own lighting, at the moment you need it.

One workspace, six ways in

Pick the integration that matches where the work happens. Artists usually start with a plugin; pipeline and tools teams reach for the API or MCP.

What each integration does

Every plugin can generate inside the tool and receive models over the Bridge. Plugins import GLB, and every model can also be exported from Studio in GLB, FBX, OBJ, or USDZ for tools you connect by hand.

ToolGenerate in the toolReceive from StudioSign-in
BlenderYesBridgeStudio account or API key
UnityYesBridgeAPI key
Unreal EngineYesBridgeAPI key
Godot 4YesBridgeAPI key
MCP serverThrough your agentNoAPI key
REST APIFrom your codeNoAPI key

The Blender add-on can use your Studio sign-in in the browser. Every plugin, and the MCP server, also accepts a hyd_live_ API key, created from your account.

Install the plugin for the tool you use most, and keep generation inside your scene.