Descript for AI agents

Descript imports and processes media through project-agent workflows, letting a team automate video and audio editing jobs instead of doing them by hand. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Video and audioOAuth 2.0 (MCP)MCP + RESTdescript.com
AUDIT LOG · DESCRIPTPOLICY: acme-support
09:41:07 · claude · u_8f2read
descript.list_jobs
List jobs✓ allowed · 212ms
09:41:08 · claude · u_8f2read
descript.get_project
Get project✓ allowed · 164ms
09:41:09 · claude · u_8f2write
descript.import_media
Import media✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
descript.cancel_job
Cancel job✕ blocked · policy: deny
EVERY DESCRIPT CALL, ON THE RECORD
01 · USE CASES

What agents do in Descript.

01

Import media into a project

Import a media file into a project so it's ready for editing or transcription.

02

Check a processing job's status

Check a job's status before waiting on a long-running export to finish.

03

Confirm before publishing a project

Publish a project once its edits are reviewed and approved for release.

02 · ACTIONS

14 Descript actions, graded by risk.

Every Descript action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

7

Look things up. Allowed by default.

  • descript.list_jobs
    List jobs
  • descript.get_project
    Get project
  • descript.list_folders
    List folders
  • descript.list_projects
    List projects
  • descript.get_drive_info
    Get drive info
  • descript.export_timeline
    Export timeline
  • descript.export_transcript
    Export transcript

write

6

Create and change things. Allow, or ask the user first.

  • descript.import_media
    Import media
  • descript.wait_for_job
    Wait for job
  • descript.publish_project
    Publish project
  • descript.import_drive_media
    Import drive media
  • descript.prompt_project_agent
    Prompt project agent
  • descript.report_upload_status
    Report upload status

destructive

1

Delete, cancel or archive. Ask first, or deny outright.

  • descript.cancel_job
    Cancel job
03 · HOW IT WORKS

Descript in three steps.

  1. 01Your users connect DescriptThey sign in to Descript on Arc0 Connect, under your brand, and approve the access you ask for.
  2. 02You set the rulesReads run, writes like “import media” can wait for the user, and “cancel job” can be denied outright.
  3. 03Any agent can actYour agent calls Descript through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('descript', {
  read: 'allow',
  write: 'ask',        // import_media
  destructive: 'deny',  // cancel_job
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How Descript connects.

Descript runs its own MCP server behind OAuth. Arc0 registers the client, users approve access on Arc0 Connect, and your agent reaches Descript through the same endpoint, policies and audit log as every other app.

The same Descript connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
OAuth 2.0 (MCP)
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use Descript from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
07 · FAQ

Descript and Arc0, answered.

Q01

Can I use Descript with Claude, ChatGPT or Cursor?

Yes. Connect Descript to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Descript actions you allow.

Q02

How do users connect Descript?

Descript runs its own MCP server behind OAuth. Arc0 registers the client, users approve access on Arc0 Connect, and your agent reaches Descript through the same endpoint, policies and audit log as every other app.

Q03

Which Descript actions can my agent take?

14 in total: 7 read, 6 write and 1 destructive, such as “import media”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in Descript?

Yes. Actions like “cancel job” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.

Q05

Can my own backend call Descript too?

Yes. The same Descript connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Descript into your agent.

Your users connect Descript once, under your brand. Your agent gets 14 actions behind your policies, with every call on the record.

Free to build · MCP + REST · Audit log on every plan