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 CrewAI 8 tools — connect in under 2 minutes

Name: Descript
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 8 Tools Framework

Connect your CrewAI agents to Descript through Vinkius, pass the Edge URL in the `mcps` parameter and every Descript tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

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.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Descript Specialist",
    goal="Help users interact with Descript effectively",
    backstory=(
        "You are an expert at leveraging Descript tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Descript "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 8 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

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.

When paired with CrewAI, Descript becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Descript tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

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 CrewAI 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 CrewAI via MCP

Follow these steps to integrate the Descript MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 8 tools from Descript

Why Use CrewAI with the Descript MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Descript through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Descript + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Descript MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Descript for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Descript, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Descript tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Descript against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Descript MCP Tools for CrewAI (8)

These 8 tools become available when you connect Descript to CrewAI 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 CrewAI

Ready-to-use prompts you can give your CrewAI 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 CrewAI

Common issues when connecting Descript to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Descript + CrewAI FAQ

Common questions about integrating Descript MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.