Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Create, edit, validate, preview, and render Shotcut projects through AI clients.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified with the GitHub account matrodrigs, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.6.0) reached the registry 21 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Tethered Trust
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Fit, compatibility and recall checks for AI agents before they buy: verdicts, evidence, receipts.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Local video editing through the Model Context Protocol.
Create, edit, validate, preview, and render saved Shotcut projects through your AI assistant. The result stays an editable .mlt timeline, with transactional writes that protect the project as you work.
Demonstration · Quick start · Documentation · Website
A short H.264 export created from a native Shotcut timeline edited through Shotcut MCP.
https://github.com/user-attachments/assets/c70f064f-17e7-403d-9bcf-689a9c616cdf
You need Python 3.10+, Shotcut (recommended 26.8.1, bundled MLT 7.41.0), and an MCP client that supports local stdio servers. Shotcut includes the required media tools, codecs, and filters. No additional Python packages are required.
| Client | Installation |
|---|---|
| Claude Desktop / MCPB-compatible client | Follow the MCPB installation and update guide. |
| Codex | Clone the repository and register the local server. |
| Claude Code | Run /plugin marketplace add matrodrigs/shotcut-mcp, then /plugin install shotcut-mcp@matrodrigs and /reload-plugins. Details and manual setup. |
| Other MCP client | Configure a local stdio server. |
The installation guide includes commands for Windows, macOS, and Linux. No pip install is required to run the server. For a source checkout, the guide also shows how to check Python and Shotcut with scripts/shotcut_mcp_server.py --check before connecting MCP.
Ask your assistant:
Run shotcut_status and shotcut_doctor. Report tool paths, versions, and failed runtime checks.
Resolve failed runtime checks before editing. See troubleshooting for recovery steps.
Provide the source folder and the destination for the saved project, then describe your edit:
Create a 1920×1080, 30 fps Shotcut project from every video in this folder.
Put narration on A1, add 12-frame crossfades, and save it as documentary.mlt. Generate a contact sheet so I can review the edit before exporting.
You can request adjustments in ordinary language. See the editing workflow and example prompts for subtitles, quality analysis, effects, and delivery.
See the full capability reference for supported edit operations.
Edits are checked against the inspected revision, validated with Melt, and backed up before atomically replacing the saved project. Unknown XML is preserved; ambiguous edits are rejected. Preview and render outputs also use temporary files and atomic promotion.
Each render uses an immutable project snapshot, so later timeline edits cannot change a running export. If export was not already requested, the client confirms the output, preset, range, and overwrite behavior first. An explicit export request does not need a second approval.
Read the transaction and recovery details and rendering behavior.
See all limitations for speed-map boundaries and recovery behavior.
| Guide | What you will find |
|---|---|
| Installation | Client setup, requirements, and readiness checks |
| Workflow and examples | From an edit request to visual review and delivery |
| Technical reference | Capabilities, tools, presets, configuration, and safety |
| Behavioral specification | Detailed contracts and compatibility boundaries |
| Architecture | Module responsibilities and dependency direction |
The MCP tool catalog lists every tool with a concise purpose. Clients receive full schemas and operation guidance at runtime; most users can work entirely through natural-language prompts.
See Contributing for the shared quality gate, real integration tests, development, and release procedures, Changelog for release changes, Issues for bugs and feature requests, and Security for private vulnerability reporting.
Released under the MIT License. This is an independent community project, not affiliated with or endorsed by Shotcut or the MLT project. Shotcut is a trademark of its respective owner; MLT is an independent open-source multimedia framework. This repository contains no Shotcut or MLT source code.
Created by matrodrigs .