Kdenlive

io.github.mhbxyzPublished by GitHub account mhbxyzv0.1.0Updated Nov 8, 2026

Inspect, edit and render Kdenlive video projects locally on Linux.

VerifiedSTDIODesktop onlyFiles & Storage Media & Design

Server details

Identifier: io.github.mhbxyz/kdenlive-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Nov 8, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account mhbxyz for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.mhbxyz%2Fkdenlive-mcp.svg)](https://sourceweft.com/mcp/io.github.mhbxyz%2Fkdenlive-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Local MCP server that lets an assistant inspect, edit and render Kdenlive video projects on Linux.

What you can do: Inspect project timelines and run media diagnostics on clips
Make safe copies of projects before changing them
Edit clips and timeline content in Kdenlive projects
Render projects using Kdenlive presets, with background renders
Check the environment for Kdenlive, MLT and FFmpeg availability
When to use it: Useful when you edit video in Kdenlive on Linux and want an assistant to read a project's timeline, make clip or timeline edits, or start renders without opening the GUI. It is not for other operating systems or for non-Kdenlive editing tools.
Requirements: Linux with Python 3.11 or newer; install the PyPI package mcp-kdenlive (the name kdenlive-mcp is an unrelated project). Kdenlive, MLT melt and FFmpeg ffprobe must be installed separately and found on PATH, or pointed to via KDENLIVE_MCP_KDENLIVE, KDENLIVE_MCP_MELT and KDENLIVE_MCP_FFPROBE. Flatpak and Snap builds need wrapper paths.

Before you install

It edits and renders project files, so changes can overwrite or alter your work; set KDENLIVE_MCP_ALLOWED_ROOTS to limit which directories it may read and write. Renders consume CPU and disk, and KDENLIVE_MCP_MAX_RENDERS controls concurrency. MCP clients may start it with a reduced environment, so pass PATH or the KDENLIVE_MCP_ variables explicitly.

Installation

In SourceWeft

Open Kdenlive in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

kdenlive-mcp

Local-first, client-agnostic MCP server for Kdenlive on Linux.

Inspect, edit and render Kdenlive projects from an AI assistant, locally on Linux: timelines, media diagnostics, safe project copies, clip edits and rendering with Kdenlive presets.

pipx install mcp-kdenlive      # NOT "kdenlive-mcp": that PyPI name is an unrelated projectkdenlive-mcp diagnose

pipx install mcp-kdenlive      # NOT "kdenlive-mcp": that PyPI name is an unrelated projectkdenlive-mcp diagnose

Start here: docs/user-guide.md (install, client setup, safety, upgrade, troubleshooting). The available tools are listed in docs/tools.md, and the planned work in the roadmap.

Requirements

Linux
Python 3.11 or newer
Kdenlive, MLT (melt) and FFmpeg (ffprobe), installed separately from your distribution. The Python package does not install them.

Install

The PyPI distribution is mcp-kdenlive. The PyPI name kdenlive-mcp belongs to an unrelated project, so pipx install kdenlive-mcp installs something else. See docs/packaging.md for virtual environments, upgrades and artifact checks.

From source

git clone https://github.com/mhbxyz/kdenlive-mcp.gitcd kdenlive-mcpuv sync            # or: python -m venv .venv && .venv/bin/pip install -e .uv run kdenlive-mcp --version

git clone https://github.com/mhbxyz/kdenlive-mcp.gitcd kdenlive-mcpuv sync            # or: python -m venv .venv && .venv/bin/pip install -e .uv run kdenlive-mcp --version

Check your environment

uv run kdenlive-mcp diagnose          # human-readable, exit status 1 if something required is missinguv run kdenlive-mcp diagnose --json   # machine-readable

uv run kdenlive-mcp diagnose          # human-readable, exit status 1 if something required is missinguv run kdenlive-mcp diagnose --json   # machine-readable

The same report is available to MCP clients through the diagnose_environment tool.

Programs are looked up on PATH. Override their location with these environment variables:

Variable	Program
`KDENLIVE_MCP_KDENLIVE`	`kdenlive` (for example an AppImage path)
`KDENLIVE_MCP_MELT`	`melt`
`KDENLIVE_MCP_FFPROBE`	`ffprobe`
`KDENLIVE_MCP_FFMPEG`	`ffmpeg` (optional)
`KDENLIVE_MCP_PROBE_TIMEOUT`	Seconds allowed for each version probe (default 10)
`KDENLIVE_MCP_ALLOWED_ROOTS`	`:`-separated absolute directories; every read and write must stay inside them (recommended, see docs/security.md)
`KDENLIVE_MCP_MAX_RENDERS`	Concurrent background renders (default 1, max 4)

Flatpak and Snap builds of Kdenlive do not expose kdenlive, melt or ffprobe on PATH. Point the variables above to executables or wrapper scripts.

Start the server

Tested clients (Claude Code, Codex CLI, OpenCode, Grok Build CLI) and copyable configurations are listed in docs/clients.md. A typical configuration:

json

{  "mcpServers": {    "kdenlive": {      "command": "uv",      "args": ["run", "--directory", "/path/to/kdenlive-mcp", "kdenlive-mcp"],      "env": { "KDENLIVE_MCP_KDENLIVE": "/usr/bin/kdenlive" }    }  }}

{  "mcpServers": {    "kdenlive": {      "command": "uv",      "args": ["run", "--directory", "/path/to/kdenlive-mcp", "kdenlive-mcp"],      "env": { "KDENLIVE_MCP_KDENLIVE": "/usr/bin/kdenlive" }    }  }}

MCP clients often start servers with a reduced environment. If tools are reported missing from a client but not from your shell, pass PATH or the KDENLIVE_MCP_* variables explicitly.

To try the server with the official MCP Inspector:

npx @modelcontextprotocol/inspector --cli uv run --directory "$PWD" kdenlive-mcp --method tools/list

npx @modelcontextprotocol/inspector --cli uv run --directory "$PWD" kdenlive-mcp --method tools/list

Development

uv syncuv run pytest            # unit + protocol tests; integration tests skip when tools are missing

uv syncuv run pytest            # unit + protocol tests; integration tests skip when tools are missing

Architecture: domain modules (environment.py, process.py) do not depend on MCP. server.py is the only MCP transport layer.

Documentation:

Source: README.md at commit 200265b

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.1.0LatestNov 8, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts