Editing the script over MCP

The generic MCP endpoint (https://api.screel.ai/mcp) exposes the script and reference documents; the ChatGPT app and Claude connector do not. Setup: Other MCP clients.

Script tools

Tool	What it does
get_script	Reads the script as blocks with ids, scene links, and a version number. Long scripts come a window at a time (start_block, max_blocks), with an explicit “N more blocks” marker.
edit_script	Replaces the whole script — send every block worth keeping. Pass the base_version from get_script; if the script changed in the editor meanwhile the write is refused, so re-read and reapply.
suggest_script_edits	Same shape, but filed as a suggestion for the user to accept. base_version is optional; an accept merges over later edits and goes stale only on a real conflict.

Keep a block’s id to keep it the same block — history and diffs then stay about the prose. Omit the id for a new block. Set scene_id (or the literal music) and scene_link_kind to link a block; a leading [scene:<id>] token in the markdown is lifted into the link as well.

Reference-document tools

list_context_bits, get_context_bit, create_context_bit, update_context_bit, suggest_context_bit_edits, add_context_bit_image, update_context_bit_image — the same documents the editor shows as reference documents, including their image banks. Full parameters: Tool reference.

Behaviour to expect

• Writes land through the same live-editing service the browser uses, and persist before the tool returns — a get_script right after edit_script reads your change.
• Collaborators see the edit arrive live, attributed to the MCP client.
• The script’s title is fixed; a title in an edit is ignored.
• Block markdown up to 10,000 characters per block over MCP.