# Descript MCP connector

Connect Descript to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot or the Elaichi Agent can import media, start edits, export transcripts and publish projects, each action logged under the person who asked.

Source: https://elaichi.ai/connectors/descript/

## Facts

| | |
| --- | --- |
| Application | Descript |
| Category | Video |
| AI tools | 15 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Descript is connected

- Export the transcript of the onboarding webinar project.
- Which publish jobs on the podcast episode finished today?
- Import yesterday's demo recording and draft a two minute edit.

## Connect Descript in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Descript.
2. Optionally set Share with, then press Connect.
3. Paste a Descript API key. One person generates a token in Descript and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Descript tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Descript MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Descript MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Descript MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Descript MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Descript MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Descript to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Descript tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Descript through Elaichi

### Turn a webinar recording into clips

Marketing. Import the webinar file into a Descript project, ask for an edit that cuts the highlights, and check whether the job has finished without opening Descript.

### Get the transcript out after recording

Podcast. Export the transcript of the latest episode and have the agent draft show notes and pull quotes from it while the edit is still running.

### Publish a how-to video once approved

Support. Start a publish job on the finished project, then fetch the published link to drop into the help article.

### Find the training video someone asked about

Enablement. Search Descript for the project by topic, pull up its details, and share the published version with the person who asked.

### Bring a demo recording in from the drive

Sales. Import the call recording from your Descript drive into a new project so the agent can draft a short edit while the deal is fresh.

### Keep an eye on long edits

Communications. List the jobs running on this week's announcement video, see which have finished, and clear out the ones that were started by mistake.

## Elaichi vs Zapier MCP vs Composio for Descript

All three can connect Descript to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Descript tools | Allow or restrict single Descript tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Descript call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Descript to Claude?

Connect Descript in Elaichi by pasting a Descript API key, which you copy from your Descript account settings. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. There is no OAuth application to register in Descript and no client ID or secret to generate. Claude asks you to sign in to Elaichi as yourself, and from then on it can work in Descript on your behalf.

### Does Descript work with ChatGPT and Cursor as well as Claude?

Yes. Once Descript is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client, and the Elaichi Agent. You connect Descript once and every client picks it up.

### What can an AI agent actually do with my Descript data?

An agent can import a recording into a Descript project, from an upload or from your Descript drive, start an edit, run a publish job, and export the transcript. It can also search your Descript projects, check whether a job has finished, and fetch the details of a published project. Short, concrete asks work best, such as export the transcript of the onboarding video.

### Does connecting Descript give the AI access to every project?

No. The agent works through the Descript account whose API key was connected, and each person signs in to Elaichi as themselves, so every call is tied to them. Elaichi can narrow what is reachable in Descript, by role or by person, and never widens it beyond what that Descript account can already do.

### Can my team share one Descript connection?

Yes. One person connects Descript in Elaichi and shares the connection with a team, and nobody else ever sees or handles the Descript API key. Each teammate still signs in to Elaichi as themselves, so the audit log names who imported, edited, or published each Descript project.

### Can I stop an agent from deleting or changing things in Descript?

Yes. Restrictions in Elaichi apply per action, such as deleting a Descript job or publishing a project, and are set on a role or on one person. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a Descript connection when someone leaves?

Offboarding that person in Elaichi ends their access to Descript at once, so they can no longer reach it from Claude, ChatGPT, Cursor, or any other client. A Descript connection shared with the team keeps working for everyone else. Disconnect Descript once in Elaichi and it is removed from every client at the same time.

### Does the Descript MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Descript is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Descript?

Yes. Both let Claude, ChatGPT or Cursor use Descript. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Descript call.

### How is Elaichi different from Composio for Descript?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Descript: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 15 Descript tools

Every tool below is callable through https://api.elaichi.ai/mcp once Descript is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Create a Descript import project media** (Create). Import media files into a new or existing Descript project and optionally create compositions. Runs asynchronously; returns a job_id for polling via GET /jobs/{job_id}. Returns: job_id, drive_id, drive_name, project_id, project_url, upload_urls.
- **Create a Descript import drive media** (Create). Import one or more media files into the Descript drive's shared workspace-level media library (not a project). Accepts URL-based imports or direct file uploads (specify content_type and file_size per item to receive a signed upload_url). Runs asynchronously; returns job_id and upload_urls. Required: add_media.
- **Create a Descript jobs agent** (Create). Use a Descript background agent to create or edit a project via a natural language prompt. Returns: job_id, drive_id, drive_name, project_id, project_url, conversation_id, resolved_model. Required: prompt. Provide either project_id to edit an existing project or project_name to create a new one.
- **List all Descript agent models** (List). List the currently available Descript agent models and aliases. Returns `availableModels` (array of canonical model ids each tagged with a cost tier: low, medium, or high) and `aliases` (array of friendly aliases each with id, resolvesTo, description, and cost). The catalog changes as models launch and retire — call this endpoint for the current…
- **Create a Descript jobs publish** (Create). Publish a Descript project composition to create a shareable link and downloadable exported media file. Runs asynchronously — poll GET /jobs/{job_id} for status; once complete, the job result includes share_url, download_url, and download_url_expires_at. Returns: job_id, drive_id, drive_name, project_id, project_url. Required: project_id.
- **Create a Descript export transcript** (Create). Export the transcript from a Descript project composition as a raw file. Supports txt, markdown, html, rtf, docx (binary), and srt formats with optional speaker labels, markers, and timecodes. Returns the raw transcript file content in the requested format (binary for docx, text otherwise). Required: project_id, format.
- **List all Descript jobs** (List). List recent Descript jobs with optional filtering by project or job type. Returns: job_id, job_type, job_state, created_at, stopped_at, drive_id, project_id, project_url, progress, result, drive_name, folder_id. Defaults to jobs created within the last 7 days; max lookback is 30 days.
- **Get single Descript job by ID** (Get). Get the status of a specific Descript job by id. Returns: job_id, job_type, job_state, created_at, stopped_at, drive_id, project_id, project_url, progress, result, drive_name, folder_id. Result fields vary by job_type; check result.status (success, error, partial) for the outcome. Required: id.
- **Delete a Descript job by ID** (Delete). Cancel a running Descript job by id. Returns an empty 204 response on success. Required: id.
- **List all Descript projects** (List). List Descript projects accessible to the authenticated user within their drive. Returns: id, name, created_at, updated_at, folder_path. Supports optional filtering by name, folder_path, created_by, and date ranges, plus sorting by name, created_at, updated_at, or last_viewed_at.
- **Get single Descript project by ID** (Get). Get detailed information about a specific Descript project by id, including all media files, compositions, and published share pages. Returns: id, name, drive_id, created_at, updated_at, folder_path, media_files, compositions, publishes. Required: id.
- **Descript searches search** (Search). Search the Descript drive for projects, folders, media files, and layout packs by query string. Matches names, composition text, transcripts, and (on Enterprise drives) visual content. Returns up to 100 results including type, name, project_id or asset_id, owner, updated_at, location, and duration. Required: query.
- **List all Descript status** (List). Check Descript API availability and validate the authentication token. Returns: drive_id, drive_name, api_version.
- **Get single Descript published project by ID** (Get). Get metadata for a published Descript project by its URL slug. Returns: download_url, download_url_expires_at, project_id, publish_type, privacy, metadata, subtitles. Also includes publisher details, privacy settings, and subtitle information as documented in the Descript API. Required: id.
- **Create a Descript edit in Descript schema** (Create). Create a one-time Import URL for Descript's Edit in Descript partner integration. Posts a project file schema backend-to-backend to the Descript API and returns import_url — a URL to redirect the user to Descript's import UI where they can initiate an audio/video transfer into a new Descript Project. Required: partner_drive_id, project_schema.
