Documentation / Advanced reference
Local Studio MCP and AI authoring
Available nowA local coding agent can exchange editable Studio project files; the website has no live MCP connection.
On this page
Which AI workflow should I use?
The PATH Project Builder skill tutorial explains how to install the supplied agent skill and produce a standalone Player path-story .json from your real public Mux IDs. It runs in your coding agent/CLI, not in the website; ordinary JSON generation does not require Studio or MCP.
If you want an editable project, the optional PATH Studio MCP is a local Node stdio server registered in your coding agent, not an online account or browser bridge. Follow the repository’s docs/STUDIO_MCP.md to build/register it locally. Ask the agent to use its graph tools, validate the draft and export_project; that tool produces a .pathproj (envelope 1.0.0), not a Player .json. A draft with missing media can be saved but is not playable.
In Studio, choose Use with Codex for the supported file-exchange instructions, then Open / import (or Open Codex .pathproj) for the exported file. Import creates a separate local copy. Resolve Issues, provide public Mux references, use preview to check the story, then Export Player .json for the independent Player. Later changes in Studio are not synchronized back to the local MCP project; download a new .pathproj before changing machines or clearing storage. Compare the formats · Preview.