For agents

Drive Supercut from an MCP client

Supercut edits video on the device it runs on, which is exactly why an agent cannot drive the website: the editing happens in a browser tab, not on a server. The desktop app solves that. It runs a Model Context Protocol server on loopback, so your own assistant can trim, caption and export real footage on your machine without a single frame leaving it.

Connect in three steps

1. 1
   Install the desktop app

   macOS or Windows, from the downloads page. The server ships inside it. The Mac App Store build is sandboxed and cannot bind a port, so use the direct download if you want MCP.

2. 2
   Open the Agent panel

   It sits in the app chrome, on both the Chat and the Editor tab. It shows the URL and the bearer token for this install.

3. 3
   Paste the snippet

   The panel gives you a ready command for Claude Code, an mcp.json block for Cursor, and a plain URL plus header for everything else.

Claude Code

claude mcp add --transport http supercut http://127.0.0.1:41414/mcp --header "Authorization: Bearer <token from the app>"

Cursor, and anything else that takes an mcp.json

{
  "mcpServers": {
    "supercut": {
      "url": "http://127.0.0.1:41414/mcp",
      "headers": { "Authorization": "Bearer <token from the app>" }
    }
  }
}

The token is per install and the header is not optional. Without it the server answers 401, which is deliberate: anything on your machine can reach loopback.

What it exposes

Project tools work from either tab. The Studio timeline adds its own tools (add and move clips, trim, split, captions, text, export) to the same list when the Editor tab is open.

• read_project

  Read the active SuperCut project: name, kind (folder or normal), clip count. No pixels.

• list_clips

  List clips in the active project: id, filename, durationSeconds, current version label. Use ids with edit_with_prompt and apply_to_clips.

• edit_with_prompt

  Run a plain-English edit on one clip through the on-device editor (same as Chat). Only the prompt text is sent to the model; footage stays on the device.

• apply_to_clips

  Run one prompt on several clips, sequentially, same as selecting those clips in a folder and hitting Run.

• export_clips

  Download current versions. Omit clipIds to export every clip. Multiple clips come back as a zip. Pro-gated, same as in-app export.

Worth knowing before you wire it up

• The app has to be running. The server starts and stops with it.
• Timeline tools need the Editor tab open. They error immediately if it is not.
• Mac App Store builds cannot run the server, because the sandbox forbids binding a port.
• Prompt and export calls hold the connection for up to 10 minutes, because the edit really runs.