How do I get my Descript API token?

Log in to your Descript account at **descript.com**. Navigate to **Settings** (click your profile icon). In the left sidebar, select **API tokens**. Click the **Create token** button, give it a descriptive name, and select the specific **Drive** you want it associated with. Copy the token immediately — it will **not** be shown again after you close the window. Paste it into the configuration field below.

Can I convert a podcast transcript into a blog post automatically?

Yes. Ask your AI agent to pull the full transcript from a Descript project, then instruct it to reformat the content into a structured blog post. It retrieves speaker labels, timestamps, and the complete text — perfect for creating show notes, summaries, or full articles from your recordings.

What if I work across multiple Descript drives?

Each API token is tied to a specific Drive. If you work across multiple drives (e.g., separate drives for different shows or clients), generate a separate token for each drive and configure multiple integrations. Your AI agent can then query projects from any of your drives.

Is this useful for agencies producing video content for clients?

Absolutely. Agencies can use the AI agent to pull transcripts across client projects, track export statuses, and retrieve download links — all from a single conversational interface. No need to log in and out of different client workspaces or manually download files from the Descript dashboard.

Descript MCP Server for VS Code Copilot 8 tools — connect in under 2 minutes

Name: Descript
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 8 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Descript and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "descript": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Descript MCP Server

Connect Descript to your AI agent and manage your video and podcast production pipeline conversationally.

GitHub Copilot Agent mode brings Descript data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 8 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

Project Management — List, search, and retrieve project details including compositions, transcripts, and media files.
Transcript Access — Pull full transcriptions from any Descript project for repurposing into blog posts, social content, or subtitles.
Media Exports — Retrieve exported audio and video files, download links, and export statuses.
Drive Organization — Navigate your Descript drives and projects to find specific recordings or compositions.

The Descript MCP Server exposes 8 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Descript to VS Code Copilot via MCP

Follow these steps to integrate the Descript MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Descript

Ask Copilot: "Using Descript, help me...". 8 tools available

Why Use VS Code Copilot with the Descript MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Descript through the Model Context Protocol.

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Descript + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Descript MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Descript MCP Tools for VS Code Copilot (8)

These 8 tools become available when you connect Descript to VS Code Copilot via MCP:

create_export

Export a project

create_transcription

Supports audio and video files. Transcribe a media file

get_project

Get project details

get_transcription

Get transcription result

list_drives

List team drives

list_exports

List project exports

list_projects

List all Descript projects

list_templates

List available templates

Example Prompts for Descript in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Descript immediately.

"List all my Descript projects."

"Get the full transcript of 'Podcast Ep 47'."

"Check if my latest video export is ready for download."

Troubleshooting Descript MCP Server with VS Code Copilot

Common issues when connecting Descript to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Descript + VS Code Copilot FAQ

Common questions about integrating Descript MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.