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.
- Connects with an API key
- Free 14-day trial
- No credit card
Export the transcript of the onboarding webinar project.
Working in Descript with Elaichi
-
List all Descript agent models
-
List all Descript jobs
-
Get single Descript job by ID
How to connect Descript to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Descript MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ 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
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Descript MCP connector for Microsoft Copilot
-
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.
https://api.elaichi.ai/mcp -
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.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
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
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Descript through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Descript is logged.
-
Marketing
Turn a webinar recording into clips
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.
-
Podcast
Get the transcript out after recording
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.
-
Support
Publish a how-to video once approved
Start a publish job on the finished project, then fetch the published link to drop into the help article.
-
Enablement
Find the training video someone asked about
Search Descript for the project by topic, pull up its details, and share the published version with the person who asked.
-
Sales
Bring a demo recording in from the drive
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.
-
Communications
Keep an eye on long edits
List the jobs running on this week's announcement video, see which have finished, and clear out the ones that were started by mistake.
Try asking
- “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.”
What connecting Descript gets you
6 screens from Elaichi, each doing one job for your Descript account.
Ask Elaichi to work across your apps.
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.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Descript projects in plain language.
Find a project, check a job, or export a transcript without opening Descript.
Copy the endpoint
AI apps
One endpoint puts Descript in every client.
Claude, ChatGPT and Cursor reach Descript through one governed endpoint, no SDK and no shared key.
Tool catalog
15 Descript tools, no code to write.
Projects, media imports, edits, jobs, transcripts and publishing, ready the moment Descript is connected.
Toolboxes
Every team gets its own Descript toolbox.
Marketing publishes, the podcast team exports transcripts, each toolbox scoped to one team.
Shared connections
Share Descript access, never the API key.
One person connects Descript, teammates work through it without seeing a credential.
Audit log
Every Descript action lands in the log.
Who imported, edited, published or deleted what in Descript, with when and which resource.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Descript digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch projects
Descript
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Descript
Queued
Workflows
A schedule turns Descript jobs into a digest.
Finished Descript jobs are fetched, grouped, drafted into a digest, approved, then posted back.
Descript health
Refreshed 4 minutes ago · every 15 minutes · from the projects collection
Projects
1,284 ↓ 12%
Jobs
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Projects created
Last 14 days
By team
Share of activity
Marketing 34%
Podcast 27%
Support 21%
Enablement 18%
Collections and dashboards
Descript health, computed on a schedule, no prompts.
Four metrics, 14 days of projects created and a team breakdown, refreshed without a model.
For IT and engineering
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.
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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Descript tools for your AI agents
15 tools are ready to call through Elaichi's MCP endpoint the moment you connect Descript, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
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 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.
Put Descript in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot