Claude can't open CapCut, and we have not verified an official Claude connector for it. What works today is an AI agent that edits the video file on your computer — it cuts pauses and filler words and writes timed captions — and then hands CapCut an MP4 and an .srt caption file.
The quickest way to get that agent is VideoStudio, the video agent built into Orkas. It comes with ffmpeg and whisper.cpp, runs on the built-in models and needs no setup; new accounts get 500 free credits. If you already use Claude Code, it can do the same job once you install those two tools, and that is the route we measured below.
CapCut documents SRT import on Desktop and Web. We have not tested this handoff end to end; the measured example in this guide covers Claude Code with ffmpeg on macOS. Claude Desktop computer use and the official Codex plug-in through Orkas remain untested.
Can Claude edit videos in CapCut?
Not directly. CapCut offers an official CapCut × Codex / ChatGPT workflow, which is separate from community MCP draft tools. We have not verified an official CapCut connector for Claude.
Claude Desktop also offers computer use to interact with applications through the screen, mouse and keyboard, when enabled and with the required app permissions. We have not tested its CapCut compatibility or editing results.
- Community draft generators. VectCutAPI (formerly CapCutAPI) is an independent open-source project that writes draft files CapCut and JianYing can open, and it includes an MCP server that Claude Code can call. Some community "capcut-mcp" projects build on it. You still open the draft in CapCut to review and export it, and CapCut doesn't publish its draft format, so an app update can break these tools. We haven't tested them inside Orkas.
- CapCut × Codex / ChatGPT (official). CapCut describes a plug-in workflow for creating and refining editable drafts with Codex. Follow CapCut’s own availability and setup requirements. It is not proof of a Claude MCP connector, and we have not tested this plug-in through Orkas.
- CapCut's own assistant. The CapCut PC app has EditPilot, a chat-style editor built into CapCut. It runs on CapCut's side, not on Claude.
- Plain files. The route that needs no integration: let an agent such as VideoStudio or Claude Code make the rough cut and a caption file, then open both in CapCut. CapCut's desktop and web editors can import an .srt file from the Captions panel.
What Claude can actually do with a video
The Claude chat app isn't the place for this: footage is large, and the edit needs programs running against your files. The work is done by an agent that runs two kinds of free tools on your computer:
- ffmpeg cuts, joins, resizes and re-encodes video, and can burn captions into the picture.
- A speech-to-text model such as whisper.cpp turns the audio into a transcript with timestamps.
VideoStudio has both built in, so you can start from your footage. Claude Code uses them once you install them. Either way, the agent can remove long pauses, drop filler words, write and burn in captions, make a vertical version, trim to a time range and export several formats. It doesn't watch the video the way you do. It works from the transcript, the audio levels and any frames it pulls out, so choices about the story, the pacing and the best take stay with you. Hand it the mechanical passes and keep the creative calls.
Edit with VideoStudio in Orkas
We recommend starting with VideoStudio. Give it your footage and the result you want, and it returns the edited video and the caption file. Besides pauses, filler words and captions, it can add voiceover and music, make vertical versions for TikTok, Reels and Shorts, and prepare versions in other languages.
- Install Orkas and sign in. New accounts get 500 free credits for the built-in models, so you can start without an API key. You can also connect your own model provider.
- Choose VideoStudio and add your clips.
- Describe the result: the length, the aspect ratio, what to keep, the caption language and the files you want back.
- Review before you finish. If you want to approve the cut first, ask to see it before it renders. Then watch the video and ask for focused changes, such as a shorter opening or a different closing shot.
A request you can adapt:
Edit [my footage] into a [60-second] video for [TikTok].
Show me the cut before you render.
Remove long pauses and filler words such as "um" and "uh".
Keep the clearest take of each point and add [English] captions.
Deliver an MP4 without burned-in captions and a matching .srt file
so I can finish the edit in CapCut.
Keep my original files unchanged.Editing footage you already have uses only the credits of the conversation model. Generating new shots costs more, and VideoStudio asks before it spends credits on them. If you would rather have Claude as the model, add your own Anthropic API key in Orkas and VideoStudio uses it; otherwise it runs on the built-in models.
Already using Claude Code? Our test with a 30-second clip
We ran Claude Code 2.1.294 inside Orkas on a Mac (Apple M4 Max), with ffmpeg 7.0 and whisper.cpp using the multilingual base model. The source stood in for a talking-head take: a 1080p clip with a computer voice reading a short script, with long pauses and four "um" and "uh" sounds left in.
The request, in plain words: remove pauses longer than 0.6 seconds but leave a quarter of a second, cut the filler words, burn in captions, and export a 16:9 and a 9:16 version. What happened:
- Claude Code first transcribed the clip with word timestamps. The small model's timestamps drifted: the first word was stamped at 0.0 seconds, although speech started at 1.5. Cutting at those times would have clipped words.
- So it changed method. It found every pause with ffmpeg's silence detection, split the audio into 17 short stretches of speech, transcribed each stretch on its own and dropped the four that held only a filler word. Every kept and removed range went into a cut list with the reason.
- It rendered the cut, transcribed the result again for the captions and burned them into both versions.
| Check | Result |
|---|---|
| Length | 29.8 s → 17.6 s |
| Filler words removed | 4 of 4 |
| Long pauses shortened | 8 |
| Caption lines with a wrong word | 2 of 11: "three ways to" became "ways too", and an "I'll" was added |
| First vertical render | Captions sat in the middle of the frame; one follow-up fixed it |
| Processing time | About 7 seconds per full run |


Two lessons carry over to real footage. Read every caption line before you publish, because a small model gets common words wrong. And expect to tune the pause threshold: a recording with room noise or music needs a different level than our clean test voice.
Set up Claude Code for the same job
- Install Claude Code and sign in. It needs a Claude plan that includes Claude Code, or an Anthropic API key.
- Install ffmpeg and whisper.cpp, plus a whisper model file. On a Mac, Homebrew has both (
brew install ffmpeg whisper-cpp); on Windows, use the official builds or a package manager. You can also ask Claude Code to install them and approve each step. - Connect Claude Code in Orkas. In the sidebar, choose Connect agents and pick Claude Code. Orkas lists the coding agents it finds on your computer and runs your installed copy with your existing sign-in.
- Point it at your footage and describe the edit. Keep the original file, ask for the cut list before it renders, and read the captions.
A request you can adapt:
In ~/Videos/take-01.mp4:
- transcribe it and save the captions as an .srt
- remove pauses longer than 0.6 s, leaving 0.25 s
- cut "um" and "uh"
- burn the captions in
- export a 16:9 and a 9:16 version next to the original
Show me the cut list before you render.Running Claude Code through Orkas instead of a bare terminal changes the surroundings, not the editing. The conversation and its files stay in one desktop window, the same chat can hand the next step to Codex or another agent, and you never type a command yourself. Orkas runs on macOS and Windows; our test ran on macOS.
Where CapCut fits
Let the agent take the passes that are the same every time, and use CapCut for the parts that need an editor's eye:
- VideoStudio or Claude Code: pauses, filler words, captions, trims, vertical and square versions, and the same job across many files.
- CapCut: music, effects, templates, transitions and the final look.
- Ask the agent to export the final rough cut as MP4 without burned-in captions, plus a UTF-8 SRT timed to that cut—not to the original footage.
- Import the MP4 into a CapCut desktop project. For captions, follow CapCut’s documented Captions → Add Captions → Import file route and select the SRT.
- Check the first and last captions, then check sync again after any new cuts. Style the editable captions in CapCut and export the finished video.
CapCut: SRT — CapCut documents SRT import on Desktop and Web. We have not tested this handoff end to end; the measured example in this guide covers Claude Code with ffmpeg on macOS. Claude Desktop computer use and the official Codex plug-in through Orkas remain untested.
Questions
Can Claude edit videos?
Not in the chat app, which isn't built for large video files. An agent that runs editing tools on your computer can: VideoStudio in Orkas has them built in and runs on the built-in models, and Claude Code can use ffmpeg and whisper.cpp once you install them. Both can cut pauses and filler words, add captions and export new formats.
Can Claude edit videos in CapCut?
Not directly. An agent such as VideoStudio or Claude Code can prepare the rough cut and timed captions, and you finish in CapCut with a separate MP4 video and SRT caption file; this does not require a Claude–CapCut connector. CapCut documents SRT import on Desktop and Web. We have not tested this handoff end to end; the measured example in this guide covers Claude Code with ffmpeg on macOS. Claude Desktop computer use and the official Codex plug-in through Orkas remain untested.
Is there an official CapCut MCP server?
We have not verified an official CapCut MCP connector for Claude. CapCut × Codex / ChatGPT is an official, separate workflow; community tools such as VectCutAPI are another route. Neither establishes that the same integration works in Orkas.
Does Claude watch the video?
Not the way a person does. It works from the transcript, the audio levels and frames it extracts, which is why choices about the story and the best take should stay with you.
Do I need Claude Code or an API key?
No. VideoStudio runs in Orkas with the built-in models, and new accounts get 500 free credits. If you already use Claude Code or have your own Anthropic API key, you can connect them instead.
Does this work on Windows?
Orkas and VideoStudio run on macOS and Windows, and so do Claude Code, ffmpeg and whisper.cpp. We ran our test on a Mac, so treat the Windows steps as untested.
What does it cost?
Orkas is free to download. Editing footage in VideoStudio uses credits for the conversation model only, and new accounts get 500 free credits; generating new shots costs more, and VideoStudio asks first. With Claude Code, ffmpeg and whisper.cpp are free and run on your computer, and Claude Code uses your Claude plan or API credits.
For the same workflow with other editors, see how to edit videos with Claude in Final Cut Pro, Premiere Pro and DaVinci Resolve. For Resolve's official MCP server, see DaVinci Resolve MCP. To run Claude Code next to Codex on the same project, see How to Run Claude Code and Codex Together.
For the official connected route, read the CapCut ChatGPT / Codex workflow guide. For a production brief, use the product-video prompt and worked example.