# How to connect Descript to OpenClaw (no API keys) > Connect Descript to OpenClaw with ClawLink in one click — 14 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/openclaw/descript The usual route to Descript access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Descript setup: install one ClawHub skill, connect Descript in the browser, and OpenClaw can call real Descript actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to Descript. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Descript** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect descript # connect Descript (browser OAuth) npx -y @useclawlink/cli actions descript # list available actions npx -y @useclawlink/cli run descript --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Descript in the [ClawLink dashboard](https://claw-link.dev/dashboard) — a one-click OAuth approval, no API keys. Verify the connection by asking OpenClaw: > Use Descript to mcp export timeline and walk me through the result in plain English. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Descript is connected in the dashboard, that agent calls the same 14 Descript tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Descript MCP for OpenClaw Looking for a Descript MCP server for OpenClaw? ClawLink connects Descript to OpenClaw and exposes 14 Descript tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Descript integration](https://claw-link.dev/hermes/descript) works the same way. ## What the OpenClaw Descript integration can do 14 Descript tools are ready for OpenClaw once the account is connected. ### All 14 Descript tools for OpenClaw | Tool | What it does | |---|---| | **Mcp export timeline** `descript_mcp_export_timeline` | Export a project composition as a timeline file for import into another DAW/NLE (Premiere | | **Mcp export transcript** `descript_mcp_export_transcript` | Export a project composition as a transcript document | | **Mcp get drive info** `descript_mcp_get_drive_info` | Returns the drive (workspace) connected to the current session, including its ID and name | | **Mcp get project** `descript_mcp_get_project` | Get a detailed project summary including all media files, compositions, and existing publishes | | **Mcp list folders** `descript_mcp_list_folders` | List folders in the drive | | **Mcp list jobs** `descript_mcp_list_jobs` | List recent jobs, optionally filtered by project or type | | **Mcp list projects** `descript_mcp_list_projects` | List projects accessible to the authenticated user | | **Mcp report upload status** `descript_mcp_report_upload_status` | Report that a specific direct upload failed, was aborted, or was abandoned so the import job | | **Mcp wait for job** `descript_mcp_wait_for_job` | Wait for a job to complete | | **Mcp import drive media** `descript_mcp_import_drive_media` | Import media files into the drive media library (not into a project) | | **Mcp import media** `descript_mcp_import_media` | Import media into a Descript project via URLs (direct links, Google Drive, Dropbox) or direct | | **Mcp publish project** `descript_mcp_publish_project` | Publish a Descript project composition as video or audio, producing a shareable URL | | **Mcp cancel job** `descript_mcp_cancel_job` | Cancel a queued or running job | | **Mcp prompt project agent** `descript_mcp_prompt_project_agent` | Agent Underlord, Descript's built-in AI editor, queries, creates, and edits Descript projects | ## Example prompts **Mcp Export Timeline** > Use Descript to mcp export timeline and walk me through the result in plain English. **Mcp Export Transcript** > Use Descript to mcp export transcript and walk me through the result in plain English. **Mcp Get Drive Info** > Use Descript to mcp get drive info and walk me through the result in plain English. **Mcp Get Project** > Use Descript to mcp get project and walk me through the result in plain English. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Descript working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a Descript app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Descript through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Descript. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Descript actions to the runtime in a format your agent can reliably use. | 14 tools for Descript are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Descript to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Descript in the browser, and the 14 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Descript skill but can't call the tools The ClawHub skill teaches OpenClaw about Descript, but the calls run through the ClawLink plugin and your connected account. Make sure Descript is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Descript from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Descript tools Descript tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Descript call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Descript returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### OAuth finished in the browser but the account is still missing Try reconnecting Descript and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete. ### Is there a OpenClaw Descript integration? Yes. ClawLink is the fastest way to connect OpenClaw to Descript: link your Descript account once in the browser and OpenClaw can call the Descript API through 14 ready-made tools — no custom code or token handling. ### How do I add Descript to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Descript skill from ClawHub, then you click Connect in the dashboard to authorize Descript. OpenClaw calls the tools from the next message — no config files or API keys to manage. ### How long does it take to connect Descript to OpenClaw? About two minutes. Sign in, click Connect next to Descript in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Descript up myself? The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Descript working from chat. ### OpenClaw installed the Descript skill but can't call the tools The ClawHub skill teaches OpenClaw about Descript, but the calls run through the ClawLink plugin and your connected account. Make sure Descript is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [DataRobot tools](https://claw-link.dev/openclaw/datarobot) — DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets. - [Chatbotkit](https://claw-link.dev/openclaw/chatbotkit) — ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications. - [Connect Just One API](https://claw-link.dev/openclaw/just-one-api) — Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.