Start exports from a conversation
Give your AI workspace a YouTube URL and let it start the same export jobs you already use in the YCD app.
Connect OpenAI, Cursor, xAI, or Claude to the YouTube comment exports you already trust. Start a job, follow its progress, and use the result in the same place where you analyze it.
No duplicate export storage. No second queue. No new file system.
Keep collection and interpretation close together. Your AI client can collect the public data, wait for the existing job to finish, and help turn the dataset into a clear next step.
Give your AI workspace a YouTube URL and let it start the same export jobs you already use in the YCD app.
Ask for status or list previous exports without switching between a chat and a dashboard.
Pair structured comment exports with summaries, themes, questions, and content research in your AI workflow.
The server exposes the existing product capabilities without redefining their contracts.
Choose OpenAI, Cursor, xAI, or Claude and add the remote MCP endpoint.
Use the secure OAuth flow, or connect with an API key when your client prefers headers.
Start an export, check progress, then use the returned file URL in the rest of your analysis.
No. MCP is the connection layer that lets an AI client use tools from another service. The installation page gives you the exact endpoint and configuration to paste.
No. It calls the existing YCD API. Existing queues, exports, formats, quota checks, billing, and public file URLs remain the source of truth.
The plugin and MCP connection are free to install. YCD usage still follows the account's existing plan, credits, and billing rules.
Not in v1. There is no matching search endpoint in the main API yet, so the MCP server does not pretend that one exists.