Skip to content

Connect Claude, ChatGPT, Claude Code or Cursor to Live Producer

Step by step: add Live Producer's remote MCP server as a custom connector in Claude, as a connector in ChatGPT's Developer mode, with claude mcp add in Claude Code or in Cursor's mcp.json; sign in, choose the company and what the app may do, and ask it about your shows.

Give the AI you already use a way into your shows, with your own sign-in. To read what a connected app may do and why it works as you, see Connected AI.

  • You have a Live Producer account and are a member of a company. See Sign in.
  • Your AI app takes a custom connector or a remote MCP server: Claude on any plan (a free plan takes one custom connector), ChatGPT on a paid plan with Developer mode, Claude Code and Cursor as they are.

Every app takes the same address, the platform’s, ending in /mcp:

https://platform.liveproducer.ai/mcp

Open Settings › Connectors, click Add custom connector, give it the name Live Producer and the address, and click Add. Then click Connect on it. In a Team or Enterprise plan an owner adds the connector for everyone, and each person connects it for themselves.

Open Settings › Connectors, turn on Developer mode under Advanced, and click Create: the name Live Producer, the address, and OAuth as the authentication. In a chat, turn the connector on under the tools; ChatGPT asks you to sign in the first time.

In a terminal:

Terminal window
claude mcp add --transport http liveproducer https://platform.liveproducer.ai/mcp

Then type /mcp in Claude Code, choose liveproducer and Authenticate.

Open Cursor Settings › Tools & MCP and add a server with the address, or put it in ~/.cursor/mcp.json:

{ "mcpServers": { "liveproducer": { "url": "https://platform.liveproducer.ai/mcp" } } }

Cursor marks it Needs login; click it.

Any app that connects to a remote MCP server over HTTP with a sign-in works the same way: give it the address. It registers itself with Live Producer and opens the sign-in below.

Your browser opens Live Producer’s sign-in: a link sent to your email, or Sign in with Apple. If you are signed in already, the next screen comes straight away.

Step 3: Choose the company and what the app may do

Section titled “Step 3: Choose the company and what the app may do”

The screen names the app and you. Under In which company, pick the company the app works in; your role there is shown beside it. Under What it may do, tick what you allow:

Box Allows
Read shows, scripts, the conventions, files and feedback reading only
Send and publish script, upload files changing the shows, as far as your role goes
Members and roles, the company’s script skill the company’s people and its script skill

Only the boxes your role allows are offered; a member with Billing alone has nothing to connect. Click Allow; Cancel connects nothing. You are back in your AI app, connected.

The consent screen: Connect Claude, the company LiveProducer with the role beside it, three boxes for what it may do, Allow and Cancel

Ask in your own words; the app picks what it needs and tells you what it did:

  • “Where does the November town hall stand?”
  • “Put this talk track in the Product section.”
  • “Give the product section to Priya and invite her.”
  • “Publish the script.”

The app asks you before it changes anything. Three ready-made prompts may be listed under Live Producer: Write a script in the house format, What is missing before the show and What do I need to prepare.

  • Your AI app lists Live Producer’s tools, and “which shows do I have?” is answered with your company’s shows.
  • Account › Connected AI on the platform lists the app with its company, what it may do, since when and last used. See Account page.

Describes Live Producer 0.330 · 10 November 2026