Shotcut MCP

Local-first editing Open source

Edit at the speed of thought.
Stay native to Shotcut.

Ask your MCP client to trim clips, add titles, relink media, or render a delivery. Shotcut MCP applies structured edits to the saved .mlt file, validates them locally, and keeps the result editable in Shotcut.

Install for your client Download latest release

shotcut-mcp-demo.mp4

Ready
Shotcut MCP demonstration Native timeline edit to H.264 export
24 FPS 1080 P H.264 EXPORT
  1. 01 — Intent“Trim the pause and export the marked range.”
  2. 02 — TransactionNative .mlt operations
  3. 03 — ResultValidated. Backed up. Editable.
Works with saved Shotcut projects MLT 7.40 Python 3.10+ Windows, macOS, and Linux

Editing workflow

From intent to an editable project.

Shotcut MCP operates on the project format itself. It does not imitate mouse clicks or hide the changes behind a hosted service.

  1. 01

    Inspect the current project

    Read the profile, tracks, clips, filters, resources, and revision before making a change.

    inspect_project → revision
  2. 02

    Plan when useful, then apply

    Dry-run the operations, review the XML diff and Melt validation result, then submit up to 500 related operations as one atomic edit.

    plan → edit × 1…500
  3. 03

    Validate, recheck, and commit

    Validate the temporary project with Melt, recheck the on-disk revision, create an isolated backup, then atomically replace the original.

    validate → recheck → save
  4. 04

    Review, render, or continue in Shotcut

    Review the result visually, start a durable export, or open the native project for hands-on adjustments. Reinspect after saving in Shotcut.

    preview | render | open

Project safety

Edits fail safely or complete cleanly.

Revision checks reject stale candidates. A per-project lock serializes MCP commits. Melt validation, isolated backups, and atomic replacement keep the last valid project on disk until the new one is ready.

Read the safety model
  1. 1
    Guard the baseRevision check · project lock
  2. 2
    Validate the candidateIn-memory edit · Melt · recheck
  3. 3
    Promote safelyIsolated backup · atomic replace

Tool coverage

What the server can actually do.

Use focused MCP tools for discovery, editing, review, rendering, and recovery. Inspect locally installed MLT services when a filter or transition needs lower-level control.

TIMELINE

Build and revise

  • Build tracks with clips, gaps, titles, markers, and subtitles
  • Refine timing with trim, split, move, roll, slip, slide, and speed
  • Apply transitions, ordered filters, and native MLT keyframes
REVIEW

Inspect, review, and recover

  • Inspect structure, resources, timing, and revisions before editing
  • Review analyzers, exact frames, contact sheets, and XML diffs
  • Relink missing media or restore a validated isolated backup
DELIVERY

Validate and deliver

  • Validate MLT services, color workflows, and available encoders
  • Render full timelines or exact ranges with durable status and history
  • Deliver chapter text and locally supported video or audio presets
See all 26 MCP tools

Installation

Choose the shortest path to a working server.

Choose your MCP client, then copy the shortest supported setup. Every option runs the same dependency-free Python server locally over stdio.

Validated stack: Shotcut 26.6.25 · MLT 7.40.0 (7.40.x family) · Python 3.10+

Project boundary: Saved .mlt files; unsaved GUI state stays in Shotcut.

Claude Code · Plugin marketplace

Install from the conversation.

Add the marketplace, install the plugin, then reload it without restarting Claude Code.

/plugin marketplace add matrodrigs/shotcut-mcp
/plugin install shotcut-mcp@matrodrigs
/reload-plugins

Common questions

Local files. Editable projects.

Does Shotcut MCP control the Shotcut interface?

No. It edits saved MLT project files directly and uses the local Shotcut, Melt, FFmpeg, and FFprobe executables for validation, previews, and rendering.

Are my videos uploaded anywhere?

No. The server runs locally over stdio. Media and project files stay on your computer unless your chosen AI client has separate upload behavior. Network resources embedded in projects are denied by default.

Can I keep editing the result in Shotcut?

Yes. The output remains a native, editable .mlt project. Let the MCP finish its transaction before reopening or saving the same project in Shotcut.

Is it affiliated with Shotcut or MLT?

No. Shotcut MCP is an independent MIT-licensed community project and is not endorsed by Shotcut or the MLT project.

Install locally

Choose your client. Keep the project native.

Start with a saved Shotcut timeline. The server inspects the project before it applies a validated revision.

Choose an install path Download the release