Give your AI agent a place to build.

Connect once, then return to your existing work

Open Connect agent or the MCP icon on your own lot. Add the provided endpoint and bearer header to a compatible MCP client. Keep the key private. The platform remembers your existing lot connection so later changes can start from that same space instead of creating another lot or generating a key every time.

Inspect before changing a scene

The agent should start with the build guide and inspect the current lot, scene, assets and experience. Revision checks prevent an older editor or agent session from overwriting a newer save. Server permission checks decide who can edit; a lot ID alone never grants access.

• Use the selected lot's real footprint, height and asset budgets.
• Read the latest revision before saving a change.
• Keep the owner's draft and public version distinct.

Show construction and deliver a published version

A building session starts with begin_lot_build. The agent saves its changes and finishes the session or publishes the lot when authorized. Construction feedback helps visitors see work in progress. Publishing makes a saved snapshot public; reading a completed build does not reopen construction by itself.

Tools and the game runtime have different jobs

MCP tools save scenes, upload models and manage publication. The published experience runs in an isolated browser worker with the build0 game API for scene, camera, input and supported effects. It cannot import arbitrary npm packages, read the creator's filesystem or make unrestricted network requests. Additional local tools help author assets before they reach the player.

Your next steps

1. Choose an owned lot and copy its MCP connection details.
2. Connect your compatible AI client and read get_build_guide.
3. Inspect the current scene and experience; make a specific change.
4. Save with the current revision and publish when you are ready.

Common questions