Hawknet target · Stable channel
Blender, under agent control.
Hawknet gives Claude Code, Codex, Cursor, or any MCP client a real connection to a running Blender session. Your agent works in the scene you have open.
macOS Linux Windows Local bridge, your machine only
One prompt, end to end
You ask
A plain-language request in your MCP client. The agent picks the blender tool and composes the calls itself.
The daemon relays
The local Hawknet daemon receives each MCP call and hands it to the addon inside your open Blender session.
Blender answers
The addon runs the change in your open scene, and a screenshot comes back so the agent verifies its own work.
Add a cube and give it a brushed copper material
blender(action: "create_primitive", primitive: "cube")
blender(action: "python", code: "…build copper material, assign to Cube…")
blender(action: "screenshot")
What your agent can do
Inspect the live scene
Objects, hierarchies, and properties come straight from the running Blender session, not from an export. The agent reads what you see.
Build and transform
Primitives, transforms, deletions, and bpy operators run in the open file. You watch each change land in the viewport.
Edit materials and data
Objects, materials, meshes, cameras, and lights are readable and editable through the addon bridge.
Verify with screenshots
Viewport and render captures come back as images, so the agent checks its own work instead of guessing.
Full Python when it matters
Beyond the built-in actions, the agent runs Python with bpy inside the session and gets structured results back.
Auditable by default
Every operation is an explicit tool call you can read back in your agent's log.
How the bridge works
A daemon on your machine, an addon in Blender
Your MCP client talks to one local daemon, and the daemon keeps a separate local bridge for each app. The Hawknet addon inside Blender picks up each command, runs it in the open session, and posts the result back. Nothing leaves your machine.
- Connection
- Local only, between the daemon and the addon
- Address
- Your machine only, never the network
- Data
- Scene data stays on your machine
- Addon
- Installed and enabled by the Hawknet installer
- Detection
- Finds Blender installs, including Snap and Flatpak
- Updates
- The daemon self-updates on the stable channel
Setup
Wired in one command
$ curl -sSfL https://hawknet.cloud.whitehawkgroup.net/install.sh | bash One installer covers every stable target. The daemon self-updates on the stable channel.
Install Hawknet
One command on macOS, Linux, or Windows. Your license key unlocks the download.
Let it wire Blender
The installer detects Blender, including Snap and Flatpak installs, and enables the Hawknet addon.
Open Blender and go
Reload your MCP client, open Blender, and the blender tool is live for your agent.
One daemon, both targets
Blender works beside Roblox Studio
The stable channel ships two targets under the same daemon. Your MCP client sees a roblox tool and a blender tool from one MCP entry, and one license covers both. An agent can move between a Studio place and a Blender scene in the same conversation.
Roblox Studio
StableRead scripts, patch Luau, build instances, run playtests, and manage Open Cloud from any MCP client.
Explore →Blender
Stable · This pageInspect scenes, drive object and material changes, and hand your agent a real 3D creation surface.
Local addon bridgeIncluded in every plan
$3.99 /month
12-day free trial. Cancel anytime. Yearly at $39.99 (Save 16%). One license covers every stable target and the experimental channel.
Already subscribed? Your next 3 months are free.
macOS, Linux, and Windows. Self-updates on the stable channel. Manage billing, license, and downloads yourself in the customer portal.
One plan. Every surface.
$3.99 per month, or $39.99 a year. 12-day free trial, cancel anytime. Already subscribed? Your next 3 months are free.