How can an AI agent control Kdenlive?

An MCP-compatible AI agent can use DCC-MCP to inspect and edit Kdenlive project files, media, subtitles, installed MLT services, and bounded renders. The agent selects the correct application instance or integration, discovers available tools, and reads their parameter definitions before acting and checking the result. These typed tools declare their inputs, outputs, and parameter types.

Kdenlive MCP and Kdenlive CLI

The Kdenlive MCP endpoint and Kdenlive CLI workflow share the same DCC-MCP adapter and tool catalog. Use dcc-mcp-cli with --dcc-type kdenlive to limit tool searches to Kdenlive. Tools declare their inputs, outputs, and parameter types so arguments can be checked before a call.

dcc-mcp-cli search --query "inspect project structure, media references, and installed MLT effects" --dcc-type kdenlive

What can an AI agent do in Kdenlive?

• inspect project structure, media references, and installed MLT effects.
• edit a new project copy with timeline clips, effects, or subtitles.
• validate project/media state and one bounded MLT render.

Capabilities change with the adapter version and loaded Skills. Search and describe tools first instead of guessing current tool names from this page.

Safe operating flow

1. Install and follow the public dcc-mcp Skill.
2. Inspect the existing CLI, adapter, and live hosts; obtain consent before installing software or changing system state.
3. Use health, dcc-types, and list to verify the Gateway and target instance.
4. Search and describe tools for the actual Kdenlive task, then follow every returned next_step.
5. Make one bounded change and verify it through host state, files, previews, logs, or rendered output.

dcc-mcp-cli health
dcc-mcp-cli dcc-types
dcc-mcp-cli list

Copyable prompt

Use the dcc-mcp Skill to connect to my Kdenlive session. Inspect the existing CLI, adapter, and live instance first; ask before installing software or changing system state. Search for and describe typed tools related to "edit a new project copy with timeline clips, effects, or subtitles", then follow every returned next_step. Do not delete, overwrite, or publish existing work. Make the smallest verifiable change, then check the result against this requirement: "validate project/media state and one bounded MLT render". Report the instance, tool, result, and evidence path.

Current availability and official source

The verified Core 0.20.39 catalog lists kdenlive at definition 0.1.0 with catalog_install_available=false. The owning repository separately released v0.1.1. Project-file tools and MLT rendering are separate from editor UI routes; the experimental native bridge requires a separately built pinned host and has no validated complete host binary. This catalog refresh performed no live editing or render acceptance.

• Kdenlive adapter repository: source of truth for installation, compatibility, host-specific capabilities, and troubleshooting.
• All AI + DCC control guides: return to every public application and pipeline integration.
• Agent workflow: shared discovery, call, validation, and diagnostic steps.

This page describes the shared Agent workflow. Each integration's repository owns its installation, API, and compatibility details.