creator-hub-mcp
Creator Hub MCP — live scene editing
The Creator Hub runs an MCP server inside the app (localhost, streamable HTTP, bearer token). Its tools read and mutate the scene that is open in the editor: changes apply to the live engine, show up in the viewport immediately, autosave to assets/scene/main.composite, and every one of them is a normal undo step for the user. The same server powers the Creator Hub's built-in AI assistant and can be exposed to any external MCP-capable tool.
Two ways you can be running:
| You are… | How the tools reach you |
|---|---|
| Inside the Creator Hub's AI assistant (Settings > Experimental > AI scene assistant; off by default) | Pre-wired. The app launches your claude / codex CLI with the server registered as creator-hub, links these skills into the scene, and injects the same rules as this skill. Nothing to set up. |
| In another tool (Claude Code terminal or VS Code extension, Cursor, Codex, Claude Desktop, …) | Connect to the running Creator Hub — see reference/connect.md. The user copies a JSON snippet from Settings > Experimental > Expose AI assistant MCP server. |
In Claude Code the tools appear as mcp__creator-hub__<tool>; inside the Creator Hub's assistant and in other clients they appear under their bare names (scene_state, create_entity, …). The connected tools are self-describing — treat the live catalog as authoritative over the table below.
RULE — the MCP is the way to change the scene graph; the file is the fallback
Never write assets/scene/main.composite, main.crdt, or scene.json by hand while the Creator Hub MCP is available. Reasons, all verified in the Creator Hub source: