Build and animate voxels with AI agents.
VoxEdit Web exposes 17 structured WebMCP site tools right inside your live browser tab. Your AI agent can sculpt voxel parts, assemble hierarchies, solve IK walk cycles, inspect pose sheets and export GLB or 1080p MP4—sharing one undo history with you, with zero server setup.
How in-tab WebMCP works
Built by Hammy as a Three.js web port of VoxEdit by The Sandbox, VoxEdit Web treats AI agents as collaborative co-authors on the exact document you have open.
No server, port or token
Tools register on document.modelContext in your open tab. There is no local stdio daemon to install, no localhost bridge socket and no pairing code to copy. Revoke access anytime with Disable agent access.
One batch, one undo step
voxedit_batch combines reusable createLibrary voxel parts, rig hierarchy edits and procedural or sparse keyframe animation into one validated commit guarded by expectedRevision.
Compact schemas & live guides
Discovery stays within tight browser context budgets. Agents fetch exact operation contracts with voxedit_operation_help (cached by contractHash) and workflow direction via voxedit_scene guide.
Visual & geometric verification
Agents frame cameras with voxedit_view, inspect voxedit_screenshot, render labeled pose sheets with voxedit_animation_preview, and verify foot contact and decoded GLB vertices with voxedit_animation_check.
Browser setup in two minutes
- Codex built-in browser: open voxedit.xyz in Codex’s browser, turn on Settings → Browser → Permissions → Enable site tools, and verify the registered
voxedit_*tools in the browser’s Site tools menu. - Chrome WebMCP testing: enable
chrome://flags/#enable-experimental-web-platform-features(and launch with--enable-features=WebMCPwhere required) sodocument.modelContextis exposed to the tab. - Try a built-in recipe first: even in an ordinary browser without WebMCP, open Agent studio to run the Copper Scout or Rolling rock public-tool recipes and inspect live tool activity.
Designing low-poly polygon meshes, subdivision surfaces or UV textures with an agent instead? Visit MeshEdit for AI Agents.
Copyable starter prompts
1. Build & rig an animated voxel character
Creates reusable voxel parts, attaches a clean hierarchy, authors a looping walk and checks silhouettes.
Use this tab's voxedit_* WebMCP site tools. First call voxedit_scene with {"detail":"summary","guide":"voxel"}. Create a new empty-rig voxel document if needed, build a charming lantern-carrying courier out of reusable createLibrary voxel parts in one voxedit_batch, attach a rigged hierarchy with an idle and walk loop, frame the camera in Render view, and inspect voxedit_screenshot and voxedit_animation_preview.
2. Refine the voxel model already open
Preserves your current canvas and undo history while improving palette contrast, silhouette and emissive accents.
Inspect the open VoxEdit document with voxedit_scene {"detail":"summary"} and voxedit_model_read. Without replacing the document, refine the current voxel model's silhouette, color palette and emissive accents using voxedit_model_edit (validate with dryRun:true first), then frame the result and take a screenshot so we can review it together.
3. Add a walk loop & verify GLB export
Solves planted limb motion, checks loop seams and decoded GLB fidelity, and exports deliverables.
Read voxedit_scene {"detail":"summary","guide":"animation"} on the open rig. Author a clean looping Walk clip using voxedit_operation_help for exact animation fields, verify loop endpoints, foot ground contact and decoded GLB agreement with voxedit_animation_check and voxedit_animation_preview (framing:"motion"), then export the animated GLB with voxedit_export.
WebMCP & agent FAQ
Do I need to run a local MCP server or enter an API key?
No. VoxEdit Web registers its voxedit_* tools directly inside the open browser tab through WebMCP (document.modelContext). There is no local bridge process, no localhost port, no pairing token and no API key stored in VoxEdit Web.
Which browsers support VoxEdit Web’s WebMCP site tools?
Codex’s built-in browser supports WebMCP site tools when Settings → Browser → Permissions → Enable site tools is turned on. Chromium browsers experimenting with native WebMCP also expose document.modelContext when launched with experimental web platform and WebMCP features enabled.
Can I undo or edit what an AI agent builds?
Yes. Every voxedit_batch or edit tool commits as one ordinary undo step on the same live canvas and timeline you use, guarded by expectedRevision so stale agent calls never overwrite your newest stroke.
How does an agent verify that a voxel animation or GLB export looks right?
Agents inspect silhouettes with voxedit_screenshot, render labeled multi-frame sheets with voxedit_animation_preview, and run voxedit_animation_check to verify loop seams, foot ground contact and decoded GLB joint and vertex agreement.
What if my agent needs low-poly polygon meshes instead of voxels?
VoxEdit Web focuses on voxels, voxel rigs and animation, as a web port by Hammy of VoxEdit by The Sandbox. For polygon mesh modeling, sculpting and UV workflows via WebMCP, use its sibling app MeshEdit at meshedit.xyz/agents/.