About youtube-transcripts
YouTube transcripts for AI agents: videos, channels, playlists, search. Timestamps, SRT, VTT
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y fetchworks-mcpAPIFY_TOKENSecretApify API token (free at console.apify.com/settings/integrations). Transcript extraction is billed to your Apify account at $2 per 1,000 delivered transcripts.Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
3Saved tool list · updated 2w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| videos | array | Yes | YouTube video URLs or bare 11-character video IDs. One transcript per video. |
| languages | array | No | Language priority list (ISO codes, e.g. ["en", "de"]). First available caption track wins. Default ["en"]. |
| translateTo | string | No | Target language code (e.g. "es") for YouTube caption auto-translation. Best-effort. |
| outputFormats | array | No | Transcript representations to include. Default ["text"] for compact tool output. |
| includeChapters | boolean | No | Include video chapters. Default false. |
| includeMetadata | boolean | No | Include title, channel, duration, views, publish date. Default true. |
| preferAutoGenerated | boolean | No | Prefer auto-generated (ASR) captions over manual ones. Default false. |
Details
The maintainer has not added details yet. Check the README in the repository.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.