Connect Descript to any MCP-compatible AI assistant — even ones without a pre-built Descript integration — using the Descript MCP server URL. Once connected, you can import media, edit with Underlord, manage projects, and publish from a conversation.

For a full overview of what the Descript MCP see Descript MCP overview; we also have official connectors for Claude and ChatGPT. To automate Descript with code, Zapier, or the command line, see the Descript API overview.

This article covers:

• Before getting started
• Connect Descript as a custom MCP
• Tips for getting the best results
• Known limitations by AI environment

Before getting started

The Descript MCP works with any AI assistant that supports custom MCP server connections. Before setting up, confirm your AI assistant meets these requirements:

• Supports custom MCP connections via URL. Your AI assistant must allow you to add a remote MCP server by entering a URL. If your assistant only supports a fixed list of integrations, the Descript MCP won't work there.
• Supports OAuth authentication. The Descript MCP uses OAuth to authenticate — no API token required. Your assistant needs to support OAuth-based MCP connections.
• Network egress enabled (Claude only). Claude disables outbound network access by default. Go to Settings → Capabilities and turn on network egress and code execution before connecting. If you don't have access to these settings, ask your Claude admin to enable them.
• Admin access (for enterprise workspaces). If you're using a team or enterprise plan on your AI assistant, your workspace admin may need to enable custom MCP connectors before the Descript MCP can be added. Check with your admin if you don't see the option to add a custom connector.

Connect Descript as a custom MCP

What you'll need

To connect Descript to any AI assistant, you'll need:

• The Descript MCP server URL: https://api.descript.com/v2/mcp
• Authentication method: OAuth
• A Descript account with access to the drive you want to connect

The MCP connects to whichever Descript drive you're currently logged into in your browser.

The exact steps vary by AI assistant, but the general flow is the same. Most assistants will have a settings area for adding custom MCPs, connectors, or tools.

General setup steps

1. Find the custom connector setting in your AI assistant. This is usually under Settings, Integrations, Connectors, Apps, or Tools. Look for an option like "Add custom connector," "Create app," "Add MCP server," or similar.
2. Enter the Descript MCP details:
   • Name: Descript (or any name you prefer)
   • MCP server URL: https://api.descript.com/v2/mcp
   • Authentication: OAuth
3. Save or create the connector. Your AI assistant may show a security warning about custom MCP servers — this is standard for any third-party connector.
4. Sign in to Descript when prompted. A browser page will open asking you to sign in and grant the AI assistant access. The MCP connects to whichever Descript drive you're currently logged into.
5. Click Allow to grant access. You'll be redirected back to your AI assistant. Descript should now appear in your list of connected tools or connectors.

To test the connection, try a prompt like: "Create a new Descript project about settling the question: since tomatoes are fruits, is tomato soup a smoothie?"

Tips for getting the best results

The MCP is scoped to a single drive. You can only create and access projects on the drive you chose when connecting. To switch drives, log out of Descript on the web, then reconnect the MCP.

Be specific in your prompts. Tell your AI assistant the project name, folder, composition, and what you want done. The more context you give, the better the result.

Your AI assistant can pull in context from other tools. If you have other connectors set up (Google Drive, Slack, Notion, etc.), your assistant can use content from those tools to give Underlord richer instructions — for example: "Find the brief in my Google Drive called 'Q3 Campaign' and create a Descript video based on it."

Example prompts:

• "Import this video from my desktop into my 'Podcasts' folder and transcribe it"
• "Add Studio Sound and remove filler words from the second composition"
• "Find my 'Q2 Review' project and create a 60-second highlight reel"
• "Write a script about how to make great coffee, turn it into a video, and publish it"

Known limitations by AI environment

The Descript MCP follows the standard Model Context Protocol, but each AI assistant implements MCP support a little differently. Some tool calls may behave inconsistently or not work at all depending on the environment. This section tracks known issues — we'll update it as new ones are reported or resolved.

• No local export endpoint. You can publish projects to Descript web links and get back signed URLs to the mp4, but exporting local files directly via the API without publishing is not yet supported. You'll need to do this manually in Descript for now.
• YouTube URLs are not supported as import sources.
• Job history is available for 30 days. After that, job records are no longer accessible.
• Single-drive scope. Editing a project on a different drive than your connection is scoped to will return an error.

Environment-specific notes

If you've connected the Descript MCP to an AI assistant and run into issues, join the Descript API Discord to report it — we'll add known issues here as they're identified.