Connected AI tools: every MCP tool of Live Producer and the Studio

Live Producer speaks the Model Context Protocol (MCP), so the AI you already use can work with your shows. A connected AI app lists the tools under two names: Live Producer, the platform’s remote MCP server, and Live Producer Studio, the MCP server of the Mac app. This page lists every tool as the app shows it, with what it does, what it takes and who may use it. To connect, see Connect your AI and Connect your AI to the Studio; for what it all means, see Connected AI.

How to read this page

Each tool opens with three things on one line:

• Its kind. Reads changes nothing. Changes writes to the show or the company, as you would on the web, with your name and the app’s on it. Proposes shows the operator a proposal in the Spelvin window to apply or discard; nothing changes until then. The AI app sees the same in the tool’s annotations, so a read runs without asking and a change asks you first.
• Who may use it. The roles whose AI sees the tool. What the list hides, the platform refuses anyway, in words.
• The box it needs. The box on the consent screen that allows it: Read, Send and publish or Members and roles, short for the three boxes Connect your AI describes.

Then what the tool does, and what it takes: its arguments, the required ones in bold. A show is named by its title or its id, a section by its ref (s2), its number or its title, a part by its ref (p7), a shot by its name as the state lists it. A ref comes from the answer before.

Live Producer, the platform

The platform’s tools are at https://platform.liveproducer.ai/mcp, behind your own sign-in. Sixteen tools in six groups.

Shows

show_list

Reads · everyone · needs Read

The company’s shows: date, stage, the published version, what each still misses, and the sections you edit. A contributor sees the shows they edit a section in.

Takes nothing.

show_get

Reads · everyone · needs Read

One show in full: its sections and parts with their refs, the presenters, who edits each section, unpublished changes, the files it misses with their keys, and its link on the web.

Takes show.

show_create

Changes · showrunners and admins · needs Send and publish

A new show in the company: from a script in the house format, or empty with one section to start typing in.

Takes title, date (2026-11-27), markdown.

Script

script_conventions

Reads · everyone · needs Read

How this company writes a script: its script skill, and the house format with an example. The AI reads it before it writes.

Takes nothing.

script_get

Reads · everyone · needs Read

The script as Markdown in the house format: the whole draft, one section, or a published version.

Takes show, section, version.

script_send

Changes · whoever may edit the section: showrunners and admins any section, a contributor their own · needs Send and publish

A script, or one section of it, into the show’s draft. Sections and parts that match keep their identity, notes and files, and everyone with the page open sees the words land. Nothing is published by it.

Takes show, markdown, section.

script_publish

Changes · whoever may edit · needs Send and publish

The whole script as the show’s next version, as whoever may edit it does on the web. The Studio pulls a version by hand; nothing reaches a Mac by itself.

Takes show, note.

section_editors_set

Changes · showrunners and admins · needs Send and publish

Give a member a section to edit, or take it back. Someone new to the company is invited as a contributor by mail on the spot.

Takes show, section, editor (name, email or id), remove.

Files

file_list

Reads · everyone · needs Read

The company’s files: name, kind, version, size, who uploaded it and which shows use it.

Takes query.

file_upload

Changes · showrunners and admins for any part, a contributor for the parts in the sections they edit · needs Send and publish

A file for one of the show’s parts, in two steps. Without upload it starts: it answers with the address to send the bytes to and the page to drop the file on. With upload, the id the first call gave, it completes once the bytes are there. The file lands as the next version of the part’s file.

Takes show; to start: key (as show_get names it: media:eugenia, deck, lowerthird, presenter:maya) or part, filename, contentType, size; to complete: upload, sha256.

Company

company_get

Reads · everyone · needs Read

The company: its plan and term, Spelvin’s use this week, how many shows, files and people it has; for an admin also the members with their roles and the pending invitations.

Takes nothing.

member_set

Changes · admins · needs Members and roles

Give a person a role: invite them by email when they are not a member yet, or change the role they have. Editor seats are the plan’s: a seat too many is refused and says where to buy one. A company keeps at least one admin.

Takes member (email, name or id), role (admin, showrunner, contributor, billing), firstName, lastName.

skill_update

Changes · showrunners and admins · needs Members and roles

The company’s script skill: how its shows are written, read by Spelvin and handed to every connected AI. Updates the default skill, the one named, or makes one when the company has none.

Takes markdown, skill, name, summary.

Feedback

feedback_list

Reads · everyone · needs Read

The public Feedback: problems and ideas about Live Producer, by kind, part and state. With mine, your own reports and their standing.

Takes kind (problem, idea), part, status (accepted, done, declined), mine.

feedback_send

Changes · everyone · needs Send and publish

A problem or an idea, as Help › Send Feedback does: filed by part with an anonymous summary, and told at once when it is already in.

Takes kind, text, details.

Spelvin

spelvin_read_script

Changes, costs actions · showrunners and admins · needs Send and publish

Have Spelvin read any text, a script in any shape, into the show’s sections and parts and merge them into the draft. Costs 10 of the company’s Spelvin actions, as on the web, so the AI uses it only when you ask for it and when script_send cannot do.

Takes show, text.

Resources and prompts

An AI app that reads MCP resources finds the same words there without a tool call:

Resource	Holds
liveproducer://company/conventions	the company’s script skill and the house format with its example
liveproducer://shows/<id>/script	a show’s draft as Markdown in the house format
liveproducer://shows/<id>/script/versions/<n>	one published version

Three ready-made prompts may appear in the app under Live Producer:

Prompt	Asks the AI to	Takes
Write a script in the house format	write or complete a show’s script in this company’s format, from notes, and send it	show, notes
What is missing before the show	read a show and say what it still needs: words, titles, files, editors, timing	show
What do I need to prepare	for a contributor: the sections you edit, what is expected of you and by when	show; every show you contribute to when left out

Live Producer Studio, the Mac

The Studio’s tools are at /mcp on the Mac’s remote control port, http://127.0.0.1:8800/mcp unless you changed the port. A tool on the same Mac as the Studio needs no sign-in and gets every tool; a tool on another device holds the remote’s token. The operator’s role on the Mac is the only one there is, so these entries name no roles. Six tools: two that see, four that prepare.

See

studio_state

Reads

What the open show looks like right now: the show’s file and web show, the sources and their health, the layers with their shots and what is on the program and in preview, Auto Live, the transition, Fade to Black, recording, streams, captions, the show clock, the pulled script and the prompter’s place, the Stream Deck’s pages.

Takes nothing.

studio_picture

Reads

A still of the program, the preview or the multiview, as a picture the AI can look at.

Takes which (program, preview, multiview).

Prepare

shot_preview

Changes the preview

Put a shot in the preview, by its name, ready for the operator’s Take. Nothing goes on the program by it. With Auto Live on it refuses, since a preview would go live.

Takes shot.

script_pull

Changes

Pull the newest version of the web show this show is connected to: the script and its files land in the show folder as the Script window’s Pull does, one undoable edit. The layers, shots and sources stay as they are.

Takes nothing.

setup_propose

Proposes

Propose changes to the show on this Mac, as Spelvin’s chat does; the changes below. They apply in order, each on the show as the ones before left it, as one edit you can undo. Nothing is removed.

Takes summary, changes.

stream_deck_layout_propose

Proposes

Place shots or actions on the keys of a Stream Deck page. The keys the operator placed themselves stay; the bottom row is the operator’s and is not placed.

Takes keys, page (show, run show, output), summary.

The changes a setup proposal can hold

Each change names its kind in op and the thing it works on by its current name in target. Names are unique in a show. Keys count from 1, left to right, the top row first.

Change	Does	Takes
rename_shot, rename_source, rename_layer	A new name.	target, to
add_placeholder	A stand-in to link later.	name, expects (camera, window, media, web, template, audio), drawing (the storyboard picture it shows until linked, such as camera-host, window-slides, media-video, lowerthird, overlay-bug)
add_layer	A new layer, at the front unless placed.	name, place (front, back), in_front_of or behind (a layer)
move_layer	A layer to another place in the stack.	target, place, in_front_of or behind
add_shot	A shot made of the show’s sources.	name, layer, elements: each a source by name and where it sits (full, pip, pip_top_left, pip_top_right, pip_bottom_left, pip_bottom_right, left_half, right_half)
move_shot	A shot to another layer.	target, layer
set_auto_out	How long a shot stays on the program after its transition in, 0.5 to 120 seconds; 0 turns Auto Out off.	target, seconds
set_brings_along	The shots on other layers, one per layer, that come with a shot when the operator asks for them, such as a presenter’s lower third with their camera.	target, along (shots by name; empty for none)
add_guest_slot	A numbered slot for a remote guest.	name
set_fields	A graphic’s fields, by their names in the page, such as name and title.	target, fields

The keys a Stream Deck layout can place

Each key takes a shot by name or an action: take, cut, fade_to_black, record, stream, captions, auto_live, start_show, next_part, previous_part, slide_forward, slide_back, talk_to_guests, next_page, previous_page. A key left out takes the next free one.

What no tool does

No connected app can take, cut, fade to black, record, stream, move the prompter or press a key: running the show is the operator’s. No tool deletes a show, removes a shot, a source or a layer, makes or reads a guest link, touches the plan, the seats or the invoices, or reaches the platform console. A proposal from the Studio’s tools never removes anything either.

How a refusal reads

A tool that cannot do what was asked says why in a sentence the AI can pass on, never a bare code: “You edit Product only. Lucas or Maya can change Welcome.” · “Section s4 is gone, the show has s1 to s3 now.” · “Your 3 included editor seats are taken. An extra seat is bought on Account › Billing.” · “Auto Live is on: a shot put in preview would go live at once.” · “This show is not connected to a web show. Connect to Web Show… in the Script window, or pick a web show there to pull from.”

Related

• Connected AI
• Connect your AI
• Connect your AI to the Studio
• Script structure
• People and roles