blog· nov 14, 2026 · 6 min
Connect Claude to Klo Cloud MCP, transfer the original footage, direct a real timeline and verify the exported video. Includes a usable first-edit brief and recovery steps.
Claude can help make editorial decisions, but a finished video needs an editor that can execute them. Klo Cloud MCP supplies that editor: source media, a persistent timeline, previews and an export. Claude can work through the cut itself using those tools, without sending the whole brief to a second autonomous agent.
Connect the editor before describing the edit #
Open Klo’s connection guide and use the remote server URL https://mcp.getklo.com/mcp. In Claude, add a custom connector, select OAuth and complete Klo’s account sign-in. Use Claude’s published identity or automatic registration where offered. Do not put passwords or bearer tokens in the conversation.
Claude’s menus and organization controls can change. Follow Anthropic’s current custom-connector instructions for your plan. Team or Enterprise access may require an administrator. Remote connectors are reached from Anthropic’s infrastructure; a local file path on your laptop is not an upload.
For a copyable setup prompt and machine-readable instructions, use the Klo agent quickstart. Once connected, ask Claude to list your Klo projects and read the account state. That verifies access. It does not prove that your footage has arrived or that a paid AI feature is enabled.
Transfer one original and verify it #
Begin with a short, representative source clip. If the assistant can access its original bytes, it can use Klo’s upload grant. If it only sees a chat thumbnail, ask for a browser upload page and select the file yourself. An accessible direct media URL is another option. Keep the source private; do not publish it just to solve an attachment problem.
Ask for the project’s media status, filename and duration after the import. An older ready file is not evidence that this upload succeeded. Wait for the new source to be ready before asking for transcript-dependent cuts.
Give Claude an editorial job it can check #
Use the footage I uploaded to make a 35–45 second vertical reel. Open with the strongest complete claim, keep the demonstration that supports it, and end on the result. Preserve the speaker’s real voice and meaning. Remove false starts and distracting s, but keep natural breaths. Use small readable captions, music only if it supports speech, and no unrelated stock footage. Show a short preview after the first cut. Keep the project editable and export only after checking picture and sound. Ask before paid generation. The important details are the audience, promise, evidence and constraints. A length alone encourages arbitrary trimming. A request such as “make it cinematic” leaves the agent guessing about pacing, sound and color.
Use short iterations with visible results #
Ask Claude to discover the exact tools it needs, read the Klo editing playbook, and inspect the source before cutting. A useful first pass contains selected speech and essential picture. Review that before typography, extra transitions or generated assets. Point feedback at a moment and a reason: “The cut before the result interrupts the sentence; keep the whole thought.”
If work is still running, preserve its job ID and poll the tool named in the result. A timeout is not evidence that nothing happened. Resume the saved project instead of requesting the same paid operation again.
Finish with the actual file #
Confirm the export belongs to the intended revision. Watch the opening, several joins and the ending; listen without relying on captions. If delivery returns a link and access code, keep the code separate from the URL. If the assistant can attach the file, verify that the attachment contains video bytes rather than an HTML preview. Connection, import, edit and delivery are four separate checks.
For a more detailed creative sequence, use the source-to-export workflow. For device choices, see Mac, Windows and Linux workflows.
Can Claude edit video through MCP? #
Claude can call editing tools supplied by a connected MCP server. Klo supplies project, timeline, preview and export operations. A connected account and accessible original footage are required; merely describing a video in chat does not import it.
Does Klo Cloud MCP require a Mac? #
The cloud editor runs on Klo servers. The assistant client must support a custom remote MCP connection with OAuth. Klo’s native desktop editor is a separate Mac application.
Why can Claude see my attachment but not edit it? #
An attachment preview may not expose the original bytes to the connector. Ask for Klo’s browser upload page or use an accessible media URL, then verify that the new file is ready in the project.