# Drive Supercut from an MCP client

> The Supercut desktop app runs a local MCP server, so Claude Code, Claude Desktop, Cursor or any MCP client can edit video on your machine.

Source: https://www.supercut.cc/mcp

The editing server is part of the desktop app, not this website. It binds to 127.0.0.1 only, it is protected by a per-install bearer token, and it drives the same on-device editor you drive by hand. Footage never leaves the machine, and no request reaches supercut.cc.

## There is also a hosted server, and it does something else

This URL, https://www.supercut.cc/mcp, is itself an MCP endpoint: Streamable HTTP, no authentication, read only. It answers questions about Supercut, which operation to use and what the exact prompt string is. It cannot touch a video file, and it never will, because the footage is not there. Connect it with `claude mcp add --transport http supercut https://www.supercut.cc/mcp`. Opening the same URL in a browser gives this page, because the response is negotiated on the Accept header.

## Connect the editing server

- Install the desktop app from https://www.supercut.cc/download
- Open the Agent panel in the app. It shows the URL and the bearer token for this install.
- Paste the snippet it gives you into your MCP client config.

Claude Code:

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

Cursor, or any client that takes an mcp.json:

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

## Transport

- Streamable HTTP at http://127.0.0.1:41414/mcp
- Authorization: Bearer <per-install token from the Agent panel>. Without the header the server answers 401.
- Methods: initialize, notifications/initialized, ping, tools/list, tools/call

## Project tools

- `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.

## Timeline tools

The Studio timeline adds its own tools (add and move clips, trim, captions, text, export). They are listed by tools/list when the Editor tab is open.

## Limits worth knowing

- The app must be running and signed in. The server starts with the app.
- Timeline tools need the Editor tab open, otherwise they error immediately.
- Mac App Store builds cannot run the server. Use the direct download build.
- Prompt and export calls can hold the connection for up to 10 minutes, because the edit really runs.

Server card: https://www.supercut.cc/mcp.json