Edit documents over MCP
Read and change a project’s script and reference documents from an MCP client. The generic MCP endpoint serves these tools. To connect a client, see Connect an MCP client.
Edit the script
Section titled “Edit the script”| Tool | What it does |
|---|---|
get_script |
Reads the script as blocks, with ids, scene links and a version number. A long script comes one window at a time (start_block, max_blocks), with a marker that says how many blocks remain. |
edit_script |
Replaces the whole script, so send every block worth keeping. Pass the base_version from get_script. If someone changed the script in the editor meanwhile, Screel refuses the write, so read it again and reapply. |
suggest_script_edits |
Takes the same blocks, but files a suggestion for you to accept. base_version is optional. An accept merges over later edits, and a suggestion no longer applies only on a real conflict. |
Keep a block’s id to keep it the same block, so history stays about the words. Omit the id for a new block.
To link a block, set scene_id (or the literal music) and scene_link_kind. A leading [scene:<id>] token in the markdown also becomes the link.
Edit reference documents
Section titled “Edit reference documents”These tools work on the reference documents the editor shows, including their image banks. See Script and reference documents.
list_context_bitsget_context_bitcreate_context_bitupdate_context_bitsuggest_context_bit_editsadd_context_bit_imageupdate_context_bit_image
What to expect
Section titled “What to expect”- Screel saves a write before the tool returns, so a
get_scriptright afteredit_scriptreads your change. - Collaborators see the edit arrive live, attributed to the MCP client.
- The script’s title is fixed, and Screel ignores a title in an edit.
- A block holds up to 10,000 characters of markdown over MCP.
