TIMEBOLT JUST GOT A BRAIN.

Edit video with
ChatGPT or Claude.

TimeBolt’s MCP server connects ChatGPT or Claude to your video transcript and timeline. Make cuts you can see, hear, and change.

01

Clean it up.

Tighten this scripted recording. Remove abandoned takes, retries, repetition, and unnecessary filler words. Keep the strongest complete take of each point and every essential step, warning, and qualification. Preserve useful pauses for on-screen actions; flag anything needing visual review. Add occasional subtle 1.15× centered punch-ins where they help without cropping important content. Add YouTube chapters timed to the finished edit. Keep selected passages in source order and preserve meaning. Use the supplied transcript and word timestamps. Keep the original framing and playback speed. Apply the edit in TimeBolt for review. After approval, export captions retimed to the finished edit from the supplied SRT; omit removed speech and use word timestamps to split cues at cuts.

About this test

The prompt at left is a reusable template; these exports were produced during iterative testing.

02

Make it shorter.

Find the strongest standalone short in this scripted recording. Aim for 30–60 seconds, with a compelling existing opening, one complete idea, and a satisfying ending. Preserve context and choose the strongest complete takes. Remove retries and repetition. Preserve pauses needed to understand on-screen actions. Suggest a title and report the selected source ranges. Keep selected passages in source order and preserve meaning. Use the supplied transcript and word timestamps. Keep the original framing and playback speed. Apply the edit in TimeBolt for review. After approval, export captions retimed to the finished edit from the supplied SRT; omit removed speech and use word timestamps to split cues at cuts.

About this test

The prompt at left is a reusable template; these exports were produced during iterative testing.

03

Multiple cameras.
One timeline.

Bring every
track together.

Your cameras. Your master audio.
One synchronized edit.

CAM 1CAM 2CAM 3MASTER AUDIO

You direct.
AI makes the cuts.

Use with ChatGPT or Claude

Edit this multicam recording: best takes only, no filler or dead air. Switch cameras to fit the content, keep my selected master track as the only audio, and add YouTube chapters. Leave the edit ready for my review.

Keep the
final say.

Change an angle. Restore a cut.
Fine-tune before you render.

Verify and fine-tuneTimeBolt · actual footage

Record in Riverside.
Refine in TimeBolt.

Sync your tracks. Clean up filler words and retakes with UMCheck. Review every camera switch. Explore Riverside editing ↗

04

Connect your AI.

Download TimeBolt ↗

In TimeBolt, open Local MCP → Connect to ChatGPT Desktop… and follow the confirmation.

Connection help

Use the desktop assistant named in TimeBolt’s Local MCP menu. Follow the connection confirmation. For Claude, fully quit and reopen the app, then review Settings → Connectors → TimeBolt. Open your media and prepare its transcript with UMCheck or a supported transcript import before asking for an edit.

Local rendering does not mean your AI conversation is offline.

Your next move.

Render your video in TimeBolt. Export an editable timeline to Final Cut Pro, Adobe Premiere Pro, or DaVinci Resolve.

A few useful answers.

AI video editing with TimeBolt.

What is the TimeBolt MCP connector?

The TimeBolt MCP connector lets ChatGPT or Claude work with your transcript and editing timeline. Ask for cuts in plain language, then review and refine the edit in TimeBolt before rendering or exporting.

Can I use ChatGPT and Claude for video editing?

Yes. Connect either supported desktop assistant through TimeBolt’s Local MCP menu. Open your media, prepare its transcript with UMCheck, and give your AI an editing prompt.

Can AI edit a multicam recording in TimeBolt?

Yes. TimeBolt supports synchronized audio and video tracks, camera switching, and timeline editing through MCP. Specify your master audio track and camera instructions, then check the cuts and switches in the multitrack editor.

Can I change the cuts AI makes?

Yes. Review the applied edit in TimeBolt, restore a passage, adjust a cut, or change a camera angle before you render. You keep the final say.

Can I export to Final Cut Pro, Premiere Pro, or DaVinci Resolve?

Yes. Export FCPXML for Final Cut Pro or XML for Adobe Premiere Pro and DaVinci Resolve. These are editable timeline exports; rendering a finished video is a separate option. Saving and timeline export require a paid TimeBolt account.

Does local editing mean my AI conversation is offline?

No. TimeBolt renders locally, but your connected AI may process transcript text and tool results through its own service. Review your assistant’s permissions and data settings.

Do I need AI to use TimeBolt?

No. TimeBolt is a standalone desktop video editor. Connecting ChatGPT or Claude is optional.

UMCheck transcription ↗TimeBolt features ↗MCP tool reference ↗Known behaviors ↗

MCP tool reference+

22 commands in the connected MCP tool listing, reviewed September 28, 2026. These are the server commands available to connected AI assistants; tool prefixes vary by client. This reference describes the exposed schemas, not a test of every operation.

ChatGPT and Claude can read and edit timelines, control multitrack projects, mute tracks, render, and export. Connect your AI →

Read the current project

CommandInputPurpose
get_file_path{}Read the open single-file media path.
get_duration{}Read timeline duration; confirm the time basis before using it as edited-output length.
get_timeline{}Read the existing single-file cuts before modifying them.
get_umcheck_transcription{}Read the prepared word-level transcript. An empty result means a transcript must be prepared or supplied.
get_predefined_filler_words_and_phrases{}Read the predefined comma-separated filler list.
get_render_queue{}Read remaining queued render tasks.

Edit a single-file timeline

CommandInputPurpose
open_file_in_timelinefilePath: stringOpen a media file by its valid path.
apply_timelinetimeline: stringApply a serialized JSON array of cuts, including keep/remove/fastforward operations, punch positions, markers, and chapter titles.

Control a multitrack project

CommandInputPurpose
open_files_in_multitrack_editorfilePaths: stringOpen camera and audio files. Pass a JSON array of valid file paths serialized as a string.
get_multitrack_timeline{}Read the existing tracks and cuts. Inspect this state before editing or camera switching.
apply_multitrack_timelinetimeline: stringApply track state and cuts, including source paths, offsets, mute state, and optional word-level transcription.
mute_or_unmute_track_in_multitrack_editortrackId: number; status: booleanMute or unmute a track. IDs start at 0; true means muted, false means unmuted.

Render and export

CommandInputPurpose
add_to_render_queue{}Queue the current single-file timeline.
start_render{}Start all queued render tasks.
start_multitrack_renderrenderToPath: stringRender the Multi-Track Editor timeline to the required output path.
generate_fcpxml{}Generate Final Cut Pro XML, save it, and return the path.
generate_fcpxml_multicam{}Generate multicam FCPXML, save it, and return the path. This is distinct from the Multi-Track Editor export below.
generate_multitrack_fcpxmlsavePath: stringExport the Multi-Track Editor project as FCPXML to the required path.
generate_xml{}Generate XML for Premiere Pro or DaVinci Resolve and return its path.
generate_xml_sequence{}Generate nested-sequence XML for Premiere Pro and return its path.
generate_multitrack_xmlsavePath: stringExport XML from the Multi-Track Editor for Premiere Pro or DaVinci Resolve.
generate_srt{}Generate SRT captions from the timeline and transcription, save the file, and return its path.

Timeline contracts

Both apply commands accept a timeline string containing a JSON array. Read and modify the existing timeline, preserving previous edits. Cover gaps explicitly with remove cuts.

Single-file cuts

Cut members: start, duration, type, punched, punchedPosition, operation, marked, and title. The description defines operation as keep, remove, or fastforward. It names type without specifying a separate enum. Punch scale is at least 1 and less than 5. Positions are center, top-left, top-right, bottom-left, bottom-right, top, bottom, left, or right. marked is boolean; title marks the start and name of a chapter or topic.

Multitrack state

Each track contains id, duration, isMuted, isVideo, sourceUrl, startPosition, timelineCuts, and optional transcription. Duration is source-file length in seconds. startPosition places the track relative to the other tracks. Transcription entries contain start, end, and word.

Each multitrack cut contains start, duration, type, punched, punchedPosition, and operation. The exposed contract allows operation: keep/remove, punched: 1, and punchedPosition: center. Do not assume the single-file punch, fast-forward, marker, or chapter fields work in multitrack.

Camera switching and master audio

For each time range, keep only the selected video angle and mark the other camera angles as removed. When video keep cuts overlap, the preview shows the topmost kept track; track 0 is at the top. Muting controls audio, not camera visibility. Preserve the intended master-audio track and account for track offsets when aligning cuts.

What remains application-side

This tool listing has no dedicated command to start UMCheck, run waveform synchronization, inspect video frames, configure render format, or export multitrack SRT/chapter files. Multitrack transcription and offsets can be represented through apply_multitrack_timeline; that is different from dedicated transcription or synchronization commands. Use UMCheck and synchronization in TimeBolt as needed, then let the assistant work with the prepared project. A file path alone does not establish visual access to camera footage.

Known behaviors and multitrack rules →

Known behaviors+

Reviewed against the connected tool descriptions September 28, 2026. Current contract rules are separated below from historical test reports. No project changes or render/export tests were performed for this review.

Multitrack rules

  • One visible angle per time range. Keep the selected camera; remove the other angles for that interval. Overlapping keeps display the topmost video track.
  • Mute is audio-only. Use mute_or_unmute_track_in_multitrack_editor with status: true to mute and false to unmute. It does not select the visible camera.
  • Preserve synchronization. Read track offsets and existing cuts before changing a project. Apply equivalent content removals across the relevant tracks while preserving the intended master audio.
  • Different write contracts. Single-file timelines support punch scale, fast-forward, markers, and chapter titles in their exposed description. The multitrack description limits punches to 1× centered and operations to keep/remove.
  • Serialized arrays. Both timeline writes take a JSON array encoded as a string. open_files_in_multitrack_editor also takes a serialized path array.
  • Output paths are required for multitrack. Use renderToPath for rendering and savePath for XML/FCPXML exports.

Empty transcript

get_umcheck_transcription returns a word-level transcript. Its description says an empty array requires UMCheck to be run in TimeBolt or a transcript to be supplied. There is no dedicated run-UMCheck tool in this listing.

Historical reports to verify in your build

These were reported in earlier connector tests. They are not newly reproduced failures or guarantees about every current build.

type: "original" on reads

Earlier reads returned this value. Do not blindly round-trip it into a write. Check the existing cut semantics and current schema; the descriptions enumerate valid operation values but do not define a separate type enum.

PayloadTooLargeError

An earlier timeline write exceeded a payload limit. The current tool descriptions do not specify the byte limit. Record the request size and exact error. Do not split a complete replacement timeline into successive partial writes without a documented append or patch contract.

Duration versus finished length

An earlier get_duration result reflected source length despite an edited timeline. Its current description says total timeline duration without defining the time basis. Do not present it as verified rendered length. Summing kept durations estimates a simple keep/remove edit; speed changes and multitrack offsets need separate treatment.

Empty write response

An earlier apply_timeline call returned no content on success. The live description does not define a response contract. Read back with get_timeline or get_multitrack_timeline and compare the intended changes before retrying a write.

Cut-boundary correction

An earlier FCPXML export matched submitted timestamps within a frame. That observation does not prove automatic acoustic correction. Validate any correction claim with the source audio and submitted, applied, and exported boundaries.

Reporting a problem

Include the TimeBolt build, assistant/client, operating system, tool name, minimal request, exact error, and read-back result. Remove private file paths and transcript content from shared reports.

Full tool reference →