Build on Starlight
The scene is a file, the app is an MCP server, and the effects and node types you add use the same API as the built-in ones.
Starlight is made to be extended. Three parts are open today, and each one works with Claude Code or any other agent.
The scene is a file
A project is a folder: project.yaml lists the walls and the brand colours, and each scene is one YAML file that holds the whole node tree. You can read it, diff it in git, generate it from a script and edit it by hand. When the file changes, the canvas changes.
The scene format gives every field.
The app is an MCP server
While Starlight runs, it serves the Model Context Protocol on this computer, for the project that is open. An agent can read and write scenes, render a still and look at it, measure type, probe pixels, make a seamless loop, start a quoted generation and export finished video. There are more than eighty tools.
- Any MCP client. The server speaks streamable HTTP at
http://127.0.0.1:4150/mcp. Claude Code finds it by itself: Starlight writes the address and the project's token into.mcp.jsonin the project folder. - This computer only. The server listens on loopback, refuses web pages (Host and Origin checks), and needs the project's bearer token.
- Spend stays yours. Generation tools quote before they spend, and a cap holds what an agent may spend without you.
- Nothing is lost. Every write makes a version first, and one tool restores it.
In the app, an agent lists the tools and their arguments itself; a public reference of every tool comes with the versioned contract below.
Extensions and effect modules
Add to Starlight from inside a project, without touching the app.
- Effect modules are shaders saved as data: an
effect.jsonand the shader code, ineffects/<name>/. Starlight writes the code around them, so a module can only do maths on pictures. It needs no trust prompt, and it reloads when you save. - Extensions are one JavaScript file each, in
extensions/<name>/index.js. They register effects, colour operations and new node types through the same plugin API the built-in ones use. A project's extensions run only after you trust them.
Ask Claude for either one ("a heat haze that moves with the music"), and it writes, checks and previews the module for you.
What comes next
We are opening Starlight further, as a platform for show content:
- Packs. Effects, motion presets, templates with slots, venue kits, fonts and Claude skills in one folder you switch on in Settings. The first is a sports pack.
- A shared library. Publish an effect to your team, then to everyone: fork it, credit it, install a pinned version.
- A stable, versioned MCP contract, documented for any client, so tools you build keep working from release to release.
Building something on Starlight? Tell us at support@tridant.io.