How to connect Claude to CapCut, and what actually works in 2026

“Claude + CapCut” is one of the most watched editing topics on YouTube this year. Four tutorials alone have passed 1.9 million views between them, and one posted on October 9 reached 304,350 views in three days. Yet the most common reply under those videos is a version of the same question: how do I actually link Claude to CapCut?

We read the code and docs behind every route people use, including the installer for CapCut’s own Codex plugin, the main open-source CapCut MCP servers, and the comment threads where people report what failed. This is what we found.

The short answer

views on the top Claude + CapCut tutorial

755,210

official CapCut connectors for Claude

0

CapCut Codex plugin version we read

0.2.1

GitHub stars on VectCutAPI

2,295

The four routes at a glance

When someone says they edited a video with Claude and CapCut, they mean one of four quite different setups. Knowing which one a tutorial uses saves hours, because they need different plans, different tools and different amounts of manual work.

Route 1: Claude makes the files, you do the import

This is what most of the viral videos actually show. Claude never opens CapCut. It writes something CapCut can read, and the creator drags it in. The top tutorial, at 755,210 views, builds motion graphics with Remotion (a code-based video library) and brings the rendered result into CapCut. Another popular one has Claude write a .cube color LUT, which CapCut accepts as a filter.

Things Claude does well in this route:

• Caption and counter files. One viewer shared the prompt behind a popular counting effect: ask for an .srt file numbering 0 to 365 with each line 0.1 seconds long. CapCut imports SRT as captions.
• Color looks. A LUT is a plain text file, so Claude can write one from a description.
• Animated titles and overlays. With Claude Code and Remotion, Claude writes the animation as code and renders it to a video file you overlay in CapCut.
• Edit lists. Claude can turn a transcript into a list of timestamps to cut, which you then apply yourself.

The catch is the last step. Every cut, every placement and every timing fix is still yours. Comments under the tutorials say so plainly:

If your bottleneck is making assets, this route is great and cheap. If your bottleneck is the editing itself, it does not touch it.

Route 2: Claude writes the CapCut draft (community MCP servers)

This is what “CapCut MCP” usually means on GitHub. CapCut keeps each project as a folder of files on your computer. Community projects learned that format and write it directly: you describe the edit, the MCP server builds a draft folder, and CapCut opens it as a normal editable project.

How the setup works

1. 1Clone VectCutAPI, install its Python requirements (Python 3.10 or newer) and FFmpeg, then start the server. It listens on localhost:9001.
2. 2Register its MCP server in Claude Code or Claude Desktop so Claude can call its tools.
3. 3Ask Claude for the edit. Calling save_draft writes a folder whose name starts with dfd_.
4. 4Copy that folder into CapCut’s drafts directory, open CapCut, review and export.

{
  "mcpServers": {
    "capcut-api": {
      "command": "python3",
      "args": ["mcp_server.py"],
      "cwd": "/path/to/VectCutAPI"
    }
  }
}

The tools cover the basics of a timeline: create a draft, add video, audio, images, text, subtitles from SRT, effects, stickers and keyframes, and read a clip’s duration. What they do not do is look at your footage. Claude places clips by the timings you or a transcript give it.

Route 3: CapCut’s official Codex plugin

CapCut now ships an official agent plugin, but it is for OpenAI’s Codex, not Claude. You start it by pasting a one-line prompt from the CapCut × Codex page into the Codex desktop app, which downloads an install file and follows it. We read that install file (plugin version 0.2.1). It says:

• It installs a plugin called CapCut@CapCut into the Codex or ChatGPT desktop app, on macOS or Windows.
• It registers an MCP server named capcut_creation at https://www.capcut.com/api/external_mcp. That is a remote server: the editing runs on CapCut’s side, and the plugin describes its job as turning “uploaded footage” into a finished video.
• You sign in to CapCut in Codex’s in-app browser before it can do anything.
• Before sign-in, it checks which country your network is in. If the answer is US, it stops and tells you authorization is not currently available from a U.S. network. The plugin stays installed but cannot connect.
• It lists two abilities: searching CapCut templates, and editing uploaded footage with cuts, pacing, captions, transitions and music.

That US check explains a lot of confusion. A September thread in r/CapCut asking how to connect Codex to CapCut got the reply “there isn’t a capcut plugin for codex afaik”, and the most visible independent article on CapCut MCP still says CapCut offers no official server. Both are understandable from a US connection, where the plugin cannot sign in.

If you are outside the US and use Codex, this is the most direct route on the list: CapCut’s own team maintains it, and it can reach CapCut’s template library, which no community server can. The trade-off is that your footage goes to CapCut’s servers and you need a CapCut account.

Why the tutorials fail on the free Claude plan

The most liked technical complaint under the October 9 tutorial, at 85 likes, is that it does not work on the free plan. Another viewer pasted Claude’s own reply after trying:

That is the whole story. Routes 2 and 4 need an AI that can read and write files on your computer. In Anthropic’s lineup that means Claude Code, which comes with the Pro, Max, Team and Enterprise plans or with pay-as-you-go API credits, or the desktop app’s file features on a paid plan. On the free plan you are limited to route 1: Claude writes text, you save it as a file and import it.

What breaks, and when

Each route has a failure mode that the demos skip.

• The draft format is not public. Route 2 depends on reverse-engineered CapCut project files. VectCutAPI ships separate profiles for different CapCut and Jianying versions, which tells you the format moves. After a CapCut update, test on a copy before trusting a draft.
• CapCut has to be closed or restarted. The capcut-ai-editor instructions say to close CapCut before the AI edits a project, and to restart CapCut if the changes do not appear.
• The AI cannot see the result. In routes 1 and 2 Claude works blind. It cannot watch the timeline, so mistakes show up only when you open the project.
• Complex edits fall apart. “It works only with simple videos like this not complex ones!” is a typical comment. Slideshows synced to a voiceover work well. Multicam, story structure and pacing by feel do not.
• Route 3 is region locked and cloud based. No sign-in on US networks, and footage leaves your computer.

There is also a fair objection from working editors. A former professional editor put it this way in r/macapps:

We agree for story-driven work. The routes above earn their keep on repetitive jobs: removing silences and retakes, captioning, resizing one video for several platforms, and syncing images to a voiceover.

Route 4: an editor your agent can drive directly

The fourth route skips CapCut. Instead of teaching an AI to write another app’s private file format, you use an editor that exposes its timeline to agents on purpose. Several exist now. We make one of them, Rushilo, so weigh this section accordingly.

What changes compared with routes 1 to 3:

• The agent works on a timeline you can watch. Claude Code or Codex connects to Rushilo as an MCP server and edits while the project is open. Every change shows on the timeline and can be undone.
• Nothing to copy between apps. No draft folders, no restarts, no import step.
• Your footage stays on your computer. Captions come from Whisper running on your machine after a one-time model download.
• You pay for your own AI. It uses the Claude Code or Codex plan you already have. Rushilo itself is $99 once, with no subscription and no credits.

And the honest limits:

• It does not open CapCut projects, and it has no CapCut template or effects library.
• Captions are burned into the exported video; it does not export separate SRT or VTT files.
• Like route 2, it needs Claude Code or Codex, so it is not a free-plan option.

Setup is a command for Claude Code, or a config snippet for Codex, copied from the app. The setup guide covers each agent.

Which route to pick

Whichever you choose, treat the AI’s output as a first cut. Watch it through before you publish. The tools have improved fast this year, but none of them watch your video the way you do.

Patel, O. (2026, October 12). How to connect Claude to CapCut, and what actually works in 2026. Rushilo. https://rushilo.com/blog/claude-capcut

About the author

Om Patel

Founder, Rushilo

Om Patel is the founder of Rushilo, a desktop video editor driven by the user's own AI, and of BigIdeasDB, a research platform that reads real complaints and reviews to help founders validate products. He writes Rushilo's research articles with the same method: primary sources, dated numbers and the words real users write.

• X (Twitter)
• BigIdeasDB