Use WizCut with ChatGPT, Claude and other AI agents

If you already talk to ChatGPT or Claude every day, you can now ask it to edit your video podcast too. Something like:

“Edit the podcast we recorded today. Two cameras and a mic recording.”

Your assistant creates the episode in WizCut, gives you a link to upload the footage, starts the edit, and comes back with a download link for the finished video. WizCut does the actual work — syncing the cameras, working out who talks when, and cutting between angles. The assistant just runs the errands for you.

Your video files never go through the chat. You upload them straight to WizCut from whatever device has them.

Before you start

You’ll need:

A WizCut account (you can create one while connecting)
An AI assistant that supports custom connectors, also called MCP servers — Claude and ChatGPT both do
Two or more camera angles from the same recording, plus any separate audio files

Connect WizCut to your assistant

You only do this once. Every assistant asks for the same address:

https://wizcut.com/api/mcp

Claude

Open Claude’s Settings and go to Connectors.
Choose Add custom connector.
Name it “WizCut” and paste https://wizcut.com/api/mcp as the URL. If there are fields for an OAuth client ID or secret, leave them empty — WizCut sets that up by itself.
Click Connect. A WizCut page opens and asks you to allow access (see what you’ll see below).
Back in Claude, make sure WizCut is switched on in the chat’s tools menu, and ask away.

Depending on your Claude plan, custom connectors may need to be turned on by your workspace owner first.

ChatGPT

ChatGPT’s menus change often, so here’s the general idea rather than exact clicks:

In ChatGPT’s settings, look under apps or connectors.
Add a custom app or connector and paste https://wizcut.com/api/mcp as its URL. Depending on your plan, ChatGPT may ask you to turn on developer mode first.
When it asks how to sign in, pick OAuth. A WizCut page opens and asks you to allow access.
Start a new chat with WizCut enabled.

Any other AI app or agent

WizCut speaks MCP (the Model Context Protocol), the standard most AI apps use to plug in outside tools. If your app lets you add a remote MCP server, give it https://wizcut.com/api/mcp and it will walk you through the same sign-in. Building your own agent? See For developers.

What you’ll see when you connect

Your assistant sends you to a WizCut page that says something like “Claude wants to use your WizCut account”. If you’re not signed in yet, you sign in (or create an account) first, then land back on that page.

Before you click Allow, check two things:

Where you go back to. The page shows the website you’ll return to after you choose — for example claude.ai or chatgpt.com. That address is the best clue to who’s asking. Known assistants get a green “Verified” label. Anything else says “Unverified app” — only continue if you started the connection yourself.
Which account. The page shows the WizCut account you’re connecting. Not the right one? Click Not you? to switch.

The app’s name comes from whoever registered it, so trust the address more than the name.

Disconnecting

To stop an assistant from using WizCut, remove the WizCut connector in that assistant’s settings.

Connected apps will show up in your WizCut settings soon; until then, email support@wizcut.com to disconnect one.

How an edit goes

Here’s a typical session, start to finish.

Ask for an edit. Tell your assistant you want an episode edited. Give it a title if you like (“Episode 42 with Anna”).
Upload your files. The assistant gives you an upload link. Open it on the device that has your recordings — a laptop, a phone, a card reader — and upload each camera’s video plus any separate audio. You don’t need to sign in on that device. If the files are spread over a few devices, open the same link on each one. The link works for 24 hours (ask for a fresh one if it runs out), and anyone who has it can upload, so don’t post it publicly.
Say when you’re done. Tell the assistant the uploads are finished. It checks that every file arrived and starts processing.
Wait a few minutes. WizCut syncs the cameras, works out who speaks when, and generates the cuts. Your assistant doesn’t watch in the background, so come back and ask “How’s my episode doing?”
Confirm who’s on which camera. WizCut looks at who moves when each person talks and works out which camera shows whom. When it’s sure, this happens on its own. When it isn’t — common with short clips, or with operated or switched cameras — your assistant shows you its best guess and asks you to confirm. You can also check it in the WizCut editor.
Review or render. By default, nothing renders until you say so. Look over the cuts in the editor (your assistant gives you the link), or just tell it to go ahead. Rendering uses your WizCut minutes, so the assistant should check with you first.
Download. When the render is done, ask for the video. You get a download link that works for a few hours — ask again any time for a fresh one.

Want it completely hands-off? Say so up front (“Just send me the finished video”). Then WizCut renders as soon as the cameras are sorted, without waiting for your review.

Prompts to try

Copy one of these into your chat:

Edit the podcast we recorded today. It’s called “Episode 12: Starting over”. We have two cameras and a separate mic recording.

I’ve uploaded everything. Can you start the edit?

How’s my episode doing?

Who did WizCut put on which camera? Show me before rendering.

The cuts feel too busy. Make it more relaxed and shorten the long pauses.

Looks good, render it.

Give me the download link for last week’s episode.

Show me my last five episodes.

Edit this one and just send me the finished video, no review needed.

What your assistant can and can’t do

Your assistant can:

Create a new episode and give you an upload link (and a new link if the old one expired)
Check how an episode is doing, including which files have finished uploading
Start processing once your files are in
Show you who WizCut thinks is on which camera, and set it from your answer
Change the pace of the edit (relaxed, balanced or dynamic) and how it handles pauses (tighten them, remove them, or keep them)
Render the final video
Get you a download link, plus links to the episode in the WizCut editor
List your recent episodes

Your assistant can’t:

Take video files in the chat — footage always goes through the upload link
Move individual cuts or pick a camera for a specific moment. Do that in the WizCut editor; your assistant gives you the link.
Retry an episode that failed, delete episodes, or change your plan. Do those in the WizCut app.
Reach anything outside your own WizCut account

Tell us what you think

Tell your assistant what you think — it can pass your feedback straight to us. Something like “Tell WizCut the cuts on the wide shot felt late” works. We read all of it, and it’s the fastest way to shape what we build next.

Privacy

WizCut never sees your conversation. We only see the requests your assistant makes on your behalf, like “create an episode” or “get the download link”, and only for the account you connected.

What happens to your files is the same as when you use WizCut directly: see our privacy policy.

For developers

Want to wire WizCut into your own agent? The MCP server is at https://wizcut.com/api/mcp (Streamable HTTP).

Authentication. Two options:

OAuth 2.1 with dynamic client registration and PKCE. Call the server without a token and you get a 401 whose WWW-Authenticate header points to the protected resource metadata. Any MCP client that follows the authorization spec handles this for you.
An API key for your own agents. Create a wc_live_ key on the settings page and send it as a header:
```
Authorization: Bearer wc_live_your_key_here
```

A token or key gives access to the whole WizCut account, so keep it as safe as a password.

The tools are create_episode, create_upload_link, get_episode_status, start_processing, get_speaker_mapping, set_speaker_mapping, recut_episode, render_episode, get_download_link and list_episodes. They sit on top of the WizCut API, so the same rules apply. Prefer calling the API directly? The OpenAPI 3.1 spec is at https://wizcut.com/openapi.json — handy for code generators and agent platforms that import one.

Testing. The MCP Inspector is the quickest way to poke at the tools:

npx @modelcontextprotocol/inspector

Pick the Streamable HTTP transport, enter https://wizcut.com/api/mcp, and add an Authorization: Bearer wc_live_… header. Keep in mind that this is your real account: tool calls create real episodes, and renders use real minutes.

Questions or ideas? Email support@wizcut.com.