Use the transcript to propose clip candidates, then cut selected moments in Descript through Underlord or its editor. Review the rendered video and captions for context and accuracy before approving any publication.
Independent review. Unpaid; no partnership with the tools on this page. Based on public documentation and research. Trademarks identify their owners’ products. Disclosure.
Editorial shortlist
Compare your options.
For selecting short clips from a long recording.
Review lost context, speaker framing and caption errors. Choose one for editing a reviewed video draft; switching may need setup changes.
Editorial judgment, not a personal-use endorsement or performance score. These are alternatives for the named role, not three required stack components. Vendors did not pay for, request or approve these positions.
Editable story comes before automated clip volume. A lower-ranked option may fit your constraints better; compare the conditions stated on each card before choosing.
Setup and portability: Confirm media rights, output specifications and exports. Do not assume project interchange or equivalent API support.
Reviewed 2026-10-21. This page applies a shared comparison for “editing a reviewed video draft” to the stated task and constraints. It is documentation-based editorial guidance, not three new hands-on tests. We weigh value for the job, distinct capabilities, replacement limits, technical effort and interoperability. Check current plan terms before adopting or switching.
Cuts the clips with Underlord edits through the Descript MCP server, or by hand in the editor
Descript’s example prompts include “create a 60-second highlight reel”. The MCP server publishes to a Descript web link; it doesn’t list local video export.
Confirmed = vendor-documented, not Ion-tested. Human and AI-platform steps are proposed roles.
Human approval
You approve every clip before it goes out.
Watch out for
Imports use Descript media minutes, and the MCP server publishes to a Descript web link rather than exporting a local file. Approve each clip before it goes anywhere.
Starter prompt
Import this recording into Descript and transcribe it. Read the transcript and propose five to ten clips of 30 to 60 seconds, each with timestamps, a hook line and a caption. Wait for my picks before cutting anything. I will approve every clip and caption before it is posted.
Written for this workflow. Paste it into your AI platform and adjust it to your situation.
Descript: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; Descript: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it
Descript: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; Descript: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it
Descript: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; Descript: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it
Descript: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; Descript: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it
Gemini
To verify
Descript: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; Descript: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it
Descript: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; Descript: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it
What the platform statuses mean
Confirmed: documented access meets the recorded requirements. Inferred: a reviewed note describes a plausible, untested pairing. To verify: a connection or step is unresolved. MCP and API pairings need route-specific evidence; a plugin, CLI or API alone does not prove compatible access, credentials or permissions. These are documentation assessments, not IonBin runtime tests.
What we checked
The Descript MCP server connects through your Descript login and is limited to the Drive you pick when you authorize it. It can import media, edit with Underlord, organize projects, publish to a Descript web link, and export transcripts as text, Markdown, HTML, RTF or SRT. Underlord edits can use AI credits, and imports use media minutes. In team workspaces, an admin may need to allow custom connectors first.
Set it up
Connect Descript from Settings → Descript MCP (it has connect buttons for Claude, ChatGPT and Cursor) or by adding its server URL to your client. Pick the Drive the assistant may use; to switch Drives later, log out of Descript on the web and reconnect.
Use a direct file link, an upload, or a Google Drive or Dropbox link. YouTube links don’t work as import sources.
Use the client mode recommended by Descript and keep publishing tools behind approval. Ask for proposed cuts before spending credits on edits.
Review the actual cut, not just its transcript: preserve context around quotations, verify captions and names, and check whether the speaker or source license permits reuse. Publishing to a Descript web link is itself a sharing action; approve it separately from an edit.