creator-hub-mcp

What problem does it solve? Hand-editing a Decentraland scene's main.composite, main.crdt, or scene.json files while the Creator Hub is open silently loses changes, because the editor regenerates those files from its in-memory engine. This Skill routes every scene mutation through the Creator Hub's built-in MCP server so edits apply to the live engine, autosave correctly, and remain undoable for the user. ## Core Features & Use Cases - Live scene graph editing: Create, reparent, and delete entities and set or remove components (Transform, GltfContainer, LightSource, and more) through tools like create_entity, set_component, and scene_state, with every change visible in the editor viewport. - Smart Item catalog integration: Search the asset-packs catalog with search_catalog and place fully wired Smart Items (lights, doors, screens, triggers) via place_smart_item instead of manually assembling components. - Preview and verification loop: Launch the scene in the Decentraland Explorer with launch_preview, then use explorer_* tools for screenshots, walking, clicking entities, and reading logs, plus get_scene_metrics for budget checks. - Use Case: A user asks to add a spotlight above a stage in their open scene. You call search_catalog with the lights category, place the Spotlight Smart Item at the target position, verify with editor_screenshot, and the user can undo the change with Ctrl+Z. ## Quick Start Connect to the running Creator Hub using the JSON snippet from Settings > Experimental > Expose AI assistant MCP server, then ask the assistant to list the current scene entities with scene_state before making any edits.