Edits one scene at a time
A scene is read, changed and written back against its fingerprint. Twenty edits in a row do not start arguing with each other.
MCP
Your AI agent works inside the project
MCP is the protocol an agent connects to Nyxtale over. Claude, Cursor, Gemini, whichever: it edits scenes, checks them, publishes with your key.
What it does
Checks
After an edit, the same analysis the studio runs. How many scenes just went unreachable, where a branch broke off.
Publishes
Snapshot, checks, go-live. The same road the studio publishes down.
Runs on your machine
The server lives on your machine. Your key travels in a request header and is scrubbed out of everything the model gets to see.
Three steps
A key
Studio, your profile, the “Access” section. Shown once; revoke it whenever you like.
The server
In the desktop app that is one button. By hand, a single Node file with no dependencies.
Your agent
Claude Code, Claude Desktop, Cursor, Gemini CLI. The same few lines of config for every one of them.
What it will not do quietly
- Anything irreversible needs your word. Publishing, deletion and refunds will not run without explicit consent, and the refusal names exactly what was about to be touched.
- “Everything” is not an address. A selector like “*” is refused before the request leaves, and a bulk operation stops at fifty items.
- There is a read-only mode. In it no write goes through, confirmed or not.