A Complete Workflow for Editing YouTube Videos with Claude

Watching a YouTube video is fun. Editing one can be a painful task. It means comparing takes, cutting out restarts, finding the right close-up, adding readable titles and balancing speech against music. Even after the first cut, changing one explanation can mean adjusting several layers around it.

Today, Claude can help with much of this work. However, it cannot reliably carry out the timeline workflow alone. It needs a compatible video editor connected through MCP. This connection exposes the editor’s tools to Claude, so it can turn your directions into cuts, layers and other changes on a real timeline.

You can choose any editor with a compatible MCP connection, although setup and available tools vary. If you want a free option for a complete YouTube edit, invideo Editor lets Claude operate its editing controls on a professional, frame-accurate multitrack timeline. Its full manual editing suite remains available throughout, so you can shape the video yourself as well as direct Claude.

Ordinary editing through invideo MCP does not consume invideo credits. Your Claude subscription and usage allowance apply separately. Generating new images, video or audio uses invideo credits.

We’ll follow a phone review from uploaded footage to a finished six-to-eight-minute YouTube video. Our example uses presenter takes, phone close-ups, screen recordings, camera samples and battery-use notes. You can adapt the prompts to your own recordings.

Connect Claude to the editing tools

Open invideo’s connection page and select Claude. In Claude on the web or in Claude Desktop, open Customize → Connectors → + → Add custom connector. Name the connector “invideo” and enter the server URL:

https://mcp.invideo.io/mcp

Complete the connection and sign in with your invideo account when prompted. Enable the connector in the conversation you will use for editing. Team and Enterprise accounts may need an owner to add the connector for the organisation first; Claude’s current custom-connector guide explains the account-specific steps.

The Claude tab on invideo’s connection page shows the server URL and account sign-in step.

Keep invideo Editor open alongside Claude to see the changes, play the resulting timeline and make manual edits as the video develops.

Put the recordings in a project and explain the intended video

Create a project in invideo Editor and upload the recordings, screen captures and still images. You can upload directly in the Editor while working with Claude on the web. If you want Claude to import local files for you, use Claude Desktop.

Illustration based on invideo Editor: presenter takes, phone close-ups, screen recordings and camera samples are available together in the project’s media bin.

Give Claude the project link and name the timeline you want it to use.

Before asking it to cut anything, explain the audience, the result and the role of the footage:

We’re making a six-to-eight-minute, 16:9 YouTube phone review for viewers deciding whether this phone suits everyday use. The project contains presenter takes, phone close-ups, a display demonstration, an app screen recording, daylight and low-light camera samples, and battery-use notes. The review should centre on the presenter’s recorded observations and verdict. Use “Phone Review” as the main timeline. We’ll assemble the core sequence before adding graphics and music.

If you have a script, notes or an outline, share them here. They help Claude distinguish a repeated take from a second explanation that adds something useful.

Select complete takes and assemble the main sequence

Claude can inspect the footage and assemble a rough cut without you first marking every restart and pause.

Give it a coherent order and a clear basis for take selection:

Build the base cut on “Phone Review.” Open with the presenter’s strongest recorded assessment of the phone. Then arrange the review around design and display, camera performance with the uploaded samples, battery experience and the recorded verdict. Choose takes with complete, clear explanations. Remove false starts, duplicate takes and waiting between demonstrations, while keeping natural breaths and the actions needed to understand each point. Use the presenter’s dialogue as the main thread. Leave decorative graphics and music for later.

This gives Claude more useful direction than “make a good YouTube video.” It knows which material carries the explanation, what order to build and what can be removed.

For a recorded-footage example, watch Luuk Alleman’s rough-cut demonstration at 02:47. It shows a talking-head recording assembled into multiple video and audio cuts using the Editor’s built-in agent.

Luuk Alleman’s built-in-agent demonstration shows take-selection notes and assembled video and audio cuts.

Play the assembly to judge whether it makes sense to someone seeing the footage for the first time. In this review, viewers need to see the camera samples while the presenter discusses them. Removing that viewing time might shorten the video while making the assessment harder to follow.

You have full access to the Editor’s frame-accurate timeline to make any edit you deem fit. Claude reads the updated timeline before continuing, so a manual adjustment becomes part of the next stage. Explain the reason behind a creative choice when it should guide later decisions.

Refine the pacing without rebuilding approved sections

After the assembly, direct the changes that would make the sequence clearer. Name the section, describe the shot or use timestamps from the current timeline. Include what should stay.

For example, if the opening repeats the same promise twice:

Keep the opening assessment, but remove the second introduction before the design section. In the display section, retain the full scrolling demonstration and the line explaining the experience. Shorten the setup chatter before that action. Leave the camera, battery and verdict sections unchanged.

That request improves the sequence while preserving decisions you have already made. It also distinguishes a pause that adds nothing from time the viewer needs to see a result.

For a precise adjustment, use a prompt such as:

At 02:18–02:27 on the current timeline, hold the camera-module close-up until the presenter finishes the explanation. Keep the dialogue and the following cut unchanged.

The time range is illustrative. Use the timing in your own cut. You can also set the boundary by hand if you want to choose the exact frame yourself, then ask Claude to continue with the next job.

For an example of directing a revision, see BMF MEDIA’s editing walkthrough at 04:50, where the built-in agent’s opening-trim and B-roll revision notes appear alongside the timeline.

BMF MEDIA’s built-in-agent demonstration shows notes about tightening the opening beside the timeline.

Find and layer B-roll that makes the explanation visible

A presenter can explain a small change that is difficult to see in the main shot. Finding the matching close-up or screen recording, choosing the useful part and timing it over the dialogue can take several passes through the source files.

Start with searching the footage already in your project:

Find the close-up showing the phone’s rear camera module. Place it above the presenter footage during the camera-hardware explanation, keeping the presenter’s dialogue underneath. Show the detail being discussed, then return to the presenter before the camera samples.

For the next passage, the useful visual is different:

Find the app screen recording that matches the presenter’s explanation of everyday navigation. Use the portion showing the relevant scrolling and app switching over that dialogue. Keep the interface readable and leave the approved shot order unchanged.

Claude can find moments by spoken content or visual action in the project’s notebook or timeline. You describe the moment and its purpose instead of opening every recording to locate it yourself.

Screen-recording clips on V2 above the presenter on V1 and dialogue on A1. From Chris Ajtony’s Editor demonstration at 09:26, using the built-in agent.

Keep source-footage search separate from filling a gap with stock or generation. If you did not record a general establishing shot, you can ask Claude to source one or create an illustrative visual. State which route you want. For this review’s camera samples and performance demonstrations, use the actual recordings and photos so viewers see the results the presenter is discussing. Generating a new visual uses invideo credits.

Add readable titles, comparisons and captions

Claude can create and time titles, labels, photo layouts and subtitles using the Editor’s text, graphics and keyframe controls. Describe what should appear, where it belongs and how it should move. Claude can build the treatment across editable layers, then apply it consistently through the review.

Illustration based on invideo Editor: the camera callout combines separate text and graphic layers, with keyframes controlling their reveal and position.

Start with a layout that helps viewers compare the camera samples:

During the camera comparison, place the uploaded daylight and low-light photos side by side with simple “Daylight” and “Low light” labels. Keep their proportions and original colours, and show both for the full comparison explanation. Use separate editable image and text layers. Keep the subjects unobstructed.

Once the layout works, give the rest of the text a consistent treatment:

Build a consistent treatment for “Design,” “Display,” “Camera” and “Battery”: a small numbered section card with a restrained reveal. During the rear-camera close-up, add a “Camera module” callout with a thin leader line anchored to the camera cluster. Keep the text, line and section card on separate editable layers. Animate their reveal in sequence and keyframe the callout’s position to follow the phone, then remove it before the next shot. Add readable subtitles, keeping them clear of the phone interface and photo labels.

The wording, position and animation remain editable, so you can choose the exact placement or develop the motion yourself.

If a label competes with the demonstration, target that element:

Move the “Camera module” text into the empty space above the phone and adjust the leader line to stay anchored to the rear cameras. Delay the reveal until the close-up settles. Keep the subtitle style, clip timing and all other graphics unchanged.

That is a useful finishing revision because it changes how the graphic supports the shot without reopening the entire edit.

Add sound effects that follow the edit

Claude can find or generate sound effects, place them at the right moments and shape their volume and fades through the Editor’s sound-design controls. Use short cues to give section changes and graphic reveals a clear rhythm, while leaving the presenter’s voice and recorded phone demonstrations easy to hear.

Start with existing sound assets and specific moments:

Find a subtle whoosh and a soft title accent for the “Design” section-card reveal, plus a soft click for the camera-callout reveal. Place each cue on a separate SFX track and align it with the graphic’s appearance. Add short fades and keep the effects below the dialogue. Preserve the recorded sounds in the phone demonstrations and leave the picture edit unchanged.

Illustration based on invideo Editor: a title accent is timed to the “Design” reveal, with short effects on separate tracks from dialogue and music.

Describe the character of a new effect if the available assets do not fit:

Generate a short, soft tonal rise for the transition into the final verdict. Place it in the gap before the presenter starts speaking, with a gentle fade-out. Keep the existing dialogue, music and other cues unchanged.

Generating new sound effects or music uses invideo credits. Finding and arranging existing audio is a separate task.

You can also ask Claude to add an understated music bed on its own track, lower it under speech and fade it out after the verdict. Play each transition to judge whether the cue supports the pacing. If one effect feels too sharp or busy, ask Claude to shorten or soften that cue, or shape it yourself with the manual audio controls.

Finish the review, chapters and export

With picture, graphics and sound together, review the whole video for the decisions that cross layers: does each demonstration match the explanation, can viewers read the comparison, and does the music leave room for the voice? Apply any final revisions to the relevant elements before preparing delivery.

Once the timing is settled, ask Claude to make chapter markers and a matching YouTube chapter list:

Review the finished “Phone Review” timeline. Add named chapter markers at the main section boundaries and give me the matching timestamped titles for the YouTube description. Base the times on this final edit.

For the upload file, choose H.264 MP4. This reference-based illustration shows finished-video export; chapter markers are prepared on the timeline before this step.

If you subsequently shorten or rearrange a section, update the chapter times to match.

For the upload file, ask for a finished video:

Export the approved “Phone Review” timeline as a finished video for YouTube.

invideo Editor supports a rendered H.264 MP4. You can also export an editable project for Premiere Pro, Final Cut Pro or DaVinci Resolve. Specify that separately if you want to continue editing in another application.

Open the exported file before uploading it, particularly to confirm the final sound, text and beginning and ending. Add the chapter list from the final timeline to the YouTube description.

This workflow suits creators who want to direct an edit in Claude while retaining full control of a professional timeline. You can hand off the repetitive work, make creative choices through feedback or manual editing, and keep developing the same project.

Frequently asked questions

Can Claude edit YouTube videos without an MCP connection?

For the timeline workflow in this guide, Claude needs a compatible connected editor. A conversation can help plan an edit, but making cuts, arranging layers and exporting requires editing tools. Check the tools and setup offered by the editor you choose.

Is editing YouTube videos with Claude free?

Ordinary editing in invideo Editor through MCP does not consume invideo credits. Claude’s plan and usage limits apply separately, and usage varies with the model and complexity of the work. Generating images, video or audio uses invideo credits.

Do I have to find all the usable takes first?

No. You can ask Claude to inspect the recordings in the connected project, find relevant explanations or actions and assemble complete takes around your outline. Review the selection for meaning and pacing as the cut develops.

Can I use Claude on a YouTube edit I have already started?

Yes. Give Claude the invideo Editor project link and timeline name. You can also import an edit from Premiere Pro or DaVinci Resolve using an XML project file and its source media. Explain the next task and any approved sections to preserve. Claude reads the current timeline, including your manual changes, before continuing.

Can I keep editing manually or continue in a new Claude conversation?

Yes. The full manual editing suite remains available on the same timeline. For a new conversation, provide the project reference and a handover containing the brief, approved choices and remaining work. The new conversation can read the timeline, but it does not automatically inherit your previous discussion.