Claude Desktop can cut your video.

Nothing to install and no terminal — the closest thing to talking to an editor.

Setup takes a minute: add the server, then pair with the code in the editor header. After that Claude Desktop has all 59 tools.

Setup

Add Frapea to Claude Desktop

  1. 1

    Add it as a connector, not in the config file

    Settings → Connectors → Add custom connector, and paste the endpoint. This is the step most guides get wrong: claude_desktop_config.json is for LOCAL servers that Claude starts itself, and it has no field for a URL. A remote server like Frapea is a connector, and connectors are stored in the app rather than in that file.
    Settings → Connectors → Add custom connector
    https://app.frapea.com/mcp
  2. 2

    Check it in the app, not on disk

    Open the connector list and confirm Frapea is there with its tools. Looking in claude_desktop_config.json will show an empty mcpServers and tell you nothing — a working connector never appears in it.

Then, the same for every client

Pair Claude Desktop with the editor

  1. 1Open the editor and click Connect an agent in the header. It shows an eight-character code.
  2. 2Paste the whole line into Claude Desktop — the sentence, not just the code. It tells the agent which tool to call.
  3. 3Good for ten minutes, and once. If it has expired, read a fresh one.

Nothing to sign up for, and no API key on either side. The endpoint is https://app.frapea.com/mcp.

When it doesn't take

Two things go wrong, and it is almost always one of them.

1The config file shows "mcpServers": {} after adding it
That is expected. Connectors live in the application's own state, not in that file. Verify in Settings → Connectors instead.
2There is no Add custom connector button
Custom connectors are not available on every plan or every build. The fallback is the mcp-remote bridge, which wraps a remote server as a local one so the config file can hold it.

What you just handed it

59 tools, and one of them is looking at the result.

Claude Desktop now has the whole editor: it cuts, captions, sources footage it does not have, writes the titles as code, and renders frames back to itself to check the work before it says it is finished.

All 59 tools Claude Desktop can call →
Can it actually cut, or only suggest?add_clipsinsert_clipssplit_clipstrim_clipsmove_clipsremove_clipsripple_delete_rangesremove_silenceremove_wordscut_to_angleset_clip_propertiesset_keyframesmanage_transitionsmanage_effectsmanage_tracksapply_layoutgenerate_captionscreate_timelineCan it see what it made?inspect_timelineinspect_mediaget_timelineget_mediaget_transcriptsearch_mediaget_analysis_statusmanage_queueget_projectsWhere does it get what it doesn't have?search_stock_mediadownload_stock_mediasearch_soundsdownload_soundadd_sfxgenerate_voiceoverlist_voiceover_modelsorganize_mediaorganize_poolconnect_media_folderWho makes the titles?create_motion_compositionupdate_motion_compositionget_motion_compositionlist_motion_compositionsWhat am I doing while it works?open_projectnew_projectclose_projectset_active_timelineset_project_settingsundoawait_user_actionexport_projectCan it follow a person?track_faceslist_face_tracksmerge_facesbind_faceHow does it know what good looks like?read_skillrequest_ai_modelsstart_transcriptionstart_visual_indexingretry_analysisget_job_status

Using something else?

Any client that speaks MCP can drive Frapea. These are written out.

Claude.aiClaude CodeCursorVS CodeWindsurfCodex CLIGemini CLIWarp
Open the editor