Youtube Transcript MCP Da293875

MCPAI代理

提供方 toorop

AI代理 未标注 API Key 社区 / 第三方 Claude DesktopClaude

一个基于MCP协议的服务,通过yt-dlp提取YouTube视频字幕,支持Claude Desktop和HTTP客户端的双传输协议。

一句话选型结论

按资料字段整理

Youtube Transcript MCP Da293875 属于AI代理类 MCP 服务器,传输方式未标注,API Key,可直接接入 Claude Desktop、Claude,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类AI代理 传输方式未标注 鉴权API Key 部署方式未标注
GitHub 星标 1 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

AI代理
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

字幕提取Python本地部署YouTube数据处理MCP协议容器化服务多语言支持

安装与配置

未标注 API Key
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
给代理接外部能力

让代理在任务中途调用搜索、数据库等真实工具。

多步任务编排

把一串操作拆成步骤,由代理按顺序执行。

自动化重复流程

把固定流程交给代理跑,减少手工操作。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Claude Desktop、Claude,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好API Key对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在AI代理场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Youtube Transcript MCP Da293875当前 未标注 未标注 未标注 无 2026-05-17
Filesystem 560c4363 13 未标注 本地部署 无 2026-05-17
Server Everything (everything) 11 stdio · 本地进程 本地部署 有 2026-05-17
Time 7365cb6d 2 SSE · 服务端推送 远程部署 有 2026-05-18
Everything Claude Code 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Openmemory 557e1585 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

AI代理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方toorop上游标注的维护方 toorop
分类AI代理本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式API Key远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

15.4 KB
来自项目仓库与上游目录的原文,未做删改

YouTube Transcript MCP Server

A powerful MCP (Model Context Protocol) server that fetches YouTube video transcripts using yt-dlp, with dual transport support for both Claude Desktop and HTTP clients.

Features

  • ✅ Reliable: Uses yt-dlp to fetch transcripts, which is regularly updated to handle YouTube's changes
  • ✅ Containerized: Runs in a Docker container for easy deployment and portability
  • ✅ Dual Transport: Supports SSE (Server-Sent Events) for Claude Desktop AND JSON-RPC for HTTP clients
  • ✅ MCP Compliant: Implements the Model Context Protocol for seamless AI tool integration
  • ✅ Secure: Optional API key authentication for HTTP endpoints

Table of Contents

  • Quick Start
  • Docker Deployment
  • Claude Desktop Integration
  • n8n Integration
  • API Reference
  • Configuration

Quick Start

Prerequisites

  • Docker installed
  • Docker Compose installed
  • (Optional) Node.js for Claude Desktop integration

Installation

  1. Clone the repository:bash git clone <repository-url> cd youtube-transcript-mcp

  2. Configure API keys:

Create a file named api_keys.json in the root directory:json { "keys": [ "your-super-secret-api-key-here" ] }

  1. Build and run:bash docker-compose up -d --build

  2. Verify the server is running:bash curl http://localhost:5000/test_transcript?videoId=dQw4w9WgXcQ


Docker Deployment

Build and Run

From the project root directory:```bash
docker-compose up -d --build


The server will be running on `http://localhost:5000`.

### Environment Variables

Edit `docker-compose.yml` to configure:

- `AUTH_ENABLED`: Set to `false` to disable API key authentication (default: `true`)

### View Logs```bash
docker logs <container-name>

Stop the Server```bash

docker-compose down


---

---

## API Reference

The server exposes multiple endpoints supporting different transport protocols:

### Endpoints Overview

| Endpoint | Method | Transport | Authentication | Purpose |
|----------|--------|-----------|----------------|---------|
| `/sse` | GET | SSE | None* | Claude Desktop integration |
| `/` | POST | JSON-RPC 2.0 | API Key | n8n and HTTP clients |
| `/test_transcript` | GET | REST | API Key | Quick testing |

*SSE endpoints should be protected by your reverse proxy (e.g., Caddy, Nginx)

### Authentication

The server supports two authentication strategies:

**Strategy 1: Hybrid (default)**
- **SSE endpoints** (`/sse`): Not authenticated by server - protect with reverse proxy (Caddy, Nginx)
- **HTTP endpoints** (`/`, `/test_transcript`): Protected with `X-API-KEY` header
- Best for: Different clients with different auth methods (Claude Desktop via Caddy, n8n via API key)

**Strategy 2: Reverse Proxy Only**
- Set `AUTH_ENABLED=false` in `docker-compose.yml` to disable server-level auth
- Protect ALL endpoints (including `/sse`, `/`, `/test_transcript`) with your reverse proxy
- Best for: Centralized authentication, single auth mechanism for all clients

See Securing the SSE Endpoint for detailed Caddy configuration examples.

---

### Endpoint: GET /test_transcript

Simple REST endpoint for testing transcript fetching.

**Parameters:**
- `videoId` (required): YouTube video ID
- `lang` (optional): Language code (default: `en`)

**Example:**```bash
curl -H "X-API-KEY: your-api-key" \
  "http://localhost:5000/test_transcript?videoId=dQw4w9WgXcQ&lang=en"

Response:```json
{
"success": true,
"transcript": [
{
"start": "00:00:00.000",
"end": "00:00:02.500",
"text": "Hello world"
}
],
"language": "en",
"requested_language": "en"
}


**Note:** If the requested language is unavailable, the server automatically falls back to common alternatives (en→fr→es→de→pt, etc.). The `language` field shows the actual language obtained.

---

### Endpoint: POST /

MCP-compliant JSON-RPC 2.0 endpoint for n8n and other HTTP clients.

**Supported Methods:**
- `initialize`: Get server capabilities
- `tools/list`: List available tools
- `tools/call`: Execute the `get_transcript` tool

**Example - Get Transcript:**```bash
curl -X POST \
  -H "Content-Type: application/json" \
  -H "X-API-KEY: your-api-key" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "get_transcript",
      "arguments": {
        "url": "https://www.youtube.com/watch?v=dQw4w9WgXcQ",
        "language": "en"
      }
    }
  }' \
  http://localhost:5000/

Response:```json
{
"jsonrpc": "2.0",
"id": 1,
"result": {
"content": [
{
"type": "text",
"text": "{\"transcript\":[{\"start\":\"00:00:00.000\",\"end\":\"00:00:02.500\",\"text\":\"Hello world\"}],\"language\":\"en\",\"requested_language\":\"en\"}"
}
],
"structuredContent": {
"transcript": [
{
"start": "00:00:00.000",
"end": "00:00:02.500",
"text": "Hello world"
}
],
"language": "en",
"requested_language": "en"
}
}
}


**Error Response:**```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "error": {
    "code": -1,
    "message": "Failed to fetch transcript in any available language",
    "details": "No subtitles for 'pt'",
    "attempted_languages": ["en", "fr", "es", "de", "pt"]
  }
}

Claude Desktop Integration

Claude Desktop connects to MCP servers via SSE (Server-Sent Events) using the mcp-remote adapter.

Setup Instructions

Step 1: Ensure Node.js is installed

Claude Desktop uses npx to run mcp-remote. Verify Node.js installation:```bash
node --version


**Step 2: Configure Claude Desktop**

Add the following to your `claude_desktop_config.json`:

**For macOS:**```bash
~/Library/Application Support/Claude/claude_desktop_config.json

For Windows:```bash
%APPDATA%\Claude\claude_desktop_config.json


**Configuration:**

**Option 1: Without authentication (SSE endpoint publicly accessible):**```json
{
  "mcpServers": {
    "youtube-transcript": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://your-domain.com/sse"
      ]
    }
  }
}

Option 2: With HTTP Basic Auth (recommended):```json
{
"mcpServers": {
"youtube-transcript": {
"command": "npx",
"args": [
"mcp-remote",
"https://username:password@your-domain.com/sse"
]
}
}
}


**Option 3: With custom headers (API key, Bearer token, etc.):**```json
{
  "mcpServers": {
    "youtube-transcript": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "--header",
        "Authorization: Bearer your-token-here",
        "https://your-domain.com/sse"
      ]
    }
  }
}

Important: Replace https://your-domain.com with your actual server URL (e.g., behind Caddy or Nginx).

Step 3: Restart Claude Desktop

After saving the configuration, completely restart Claude Desktop.

Step 4: Verify

In a new conversation, the get_transcript tool should now be available. Test it by asking:
> "Can you fetch the transcript from this YouTube video: https://www.youtube.com/watch?v=dQw4w9WgXcQ"

Securing the SSE Endpoint

Since SSE endpoints are not authenticated by default, protect them with your reverse proxy.

Authentication Strategy

You have two options for authentication:

Option A: Protect only /sse with Caddy (recommended)
- Use Caddy to authenticate /sse/* endpoints
- Keep AUTH_ENABLED=true (default) for legacy HTTP endpoints (/, /test_transcript)
- Benefits: Claude Desktop uses Caddy auth, n8n/HTTP clients use X-API-KEY header

Option B: Protect ALL endpoints with Caddy
- Use Caddy to authenticate ALL requests
- Set AUTH_ENABLED=false in docker-compose.yml to disable server-level auth
- Benefits: Centralized authentication, single auth mechanism

Choose Option A if you want different auth methods for different clients, or Option B for unified authentication.

Example 1: Caddy with Basic Auth (SSE only - Option A)

Generate password hash:```bash
caddy hash-password


**Caddyfile:**```caddy
your-domain.com {
    reverse_proxy /sse/* localhost:5000

    # Add basic authentication
    basicauth /sse/* {
        alice $2a$14$hashed_password_here
    }
}

Claude Desktop configuration:```json
{
"mcpServers": {
"youtube-transcript": {
"command": "npx",
"args": [
"mcp-remote",
"https://alice:your-password@your-domain.com/sse"
]
}
}
}


#### Example 2: Caddy with API Key Header (SSE only - Option A)

**Caddyfile:**```caddy
your-domain.com {
    @sse_auth {
        path /sse/*
        header X-API-Key "your-secret-api-key"
    }

    handle @sse_auth {
        reverse_proxy localhost:5000
    }

    # Reject requests without valid API key
    handle /sse/* {
        respond "Unauthorized" 401
    }

    # Allow other paths without auth (or add separate rules)
    reverse_proxy localhost:5000
}

Claude Desktop configuration:```json
{
"mcpServers": {
"youtube-transcript": {
"command": "npx",
"args": [
"mcp-remote",
"--header",
"X-API-Key: your-secret-api-key",
"https://your-domain.com/sse"
]
}
}
}


#### Example 3: IP Whitelist (SSE only - Option A)

**Caddyfile:**```caddy
your-domain.com {
    @sse_trusted {
        path /sse/*
        remote_ip 192.168.1.0/24 10.0.0.0/8
    }

    handle @sse_trusted {
        reverse_proxy localhost:5000
    }

    handle /sse/* {
        respond "Forbidden" 403
    }

    reverse_proxy localhost:5000
}

Claude Desktop configuration:```json
{
"mcpServers": {
"youtube-transcript": {
"command": "npx",
"args": [
"mcp-remote",
"https://your-domain.com/sse"
]
}
}
}


#### Example 4: Protect ALL Endpoints with Basic Auth (Option B)

If you want to centralize all authentication at the reverse proxy level, use this configuration and disable server-level auth.

**Step 1: Generate password hash**```bash
caddy hash-password

Step 2: Update docker-compose.yml```yaml
version: '3.8'
services:
web:
build: .
ports:
- "5000:5000"
environment:
- AUTH_ENABLED=false # Disable server-level auth


**Step 3: Configure Caddyfile**```caddy
your-domain.com {
    # Apply basic auth to ALL endpoints
    basicauth /* {
        alice $2a$14$hashed_password_here
        bob $2a$14$another_hashed_password
    }

    reverse_proxy localhost:5000
}

Claude Desktop configuration:```json
{
"mcpServers": {
"youtube-transcript": {
"command": "npx",
"args": [
"mcp-remote",
"https://alice:your-password@your-domain.com/sse"
]
}
}
}


**n8n HTTP Request configuration:**
- **Method**: POST
- **URL**: `https://your-domain.com/`
- **Authentication**: Basic Auth
  - Username: `alice`
  - Password: `your-password`
- **Headers**: `Content-Type: application/json`
- **Body**: (same JSON-RPC format as before)

**Note:** With this setup, you no longer need to provide `X-API-KEY` headers, as all authentication is handled by Caddy.

#### Example 5: Protect ALL Endpoints with API Key Header (Option B)

Alternative approach using custom headers instead of Basic Auth.

**Step 1: Update docker-compose.yml**```yaml
version: '3.8'
services:
  web:
    build: .
    ports:
      - "5000:5000"
    environment:
      - AUTH_ENABLED=false  # Disable server-level auth

Step 2: Configure Caddyfile```caddy
your-domain.com {
@authenticated {
header X-API-Key "your-secret-api-key-here"
}

handle @authenticated {
    reverse_proxy localhost:5000
}

# Reject all requests without valid API key
handle {
    respond "Unauthorized" 401
}

}


**Claude Desktop configuration:**```json
{
  "mcpServers": {
    "youtube-transcript": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "--header",
        "X-API-Key: your-secret-api-key-here",
        "https://your-domain.com/sse"
      ]
    }
  }
}

n8n HTTP Request configuration:
- Method: POST
- URL: https://your-domain.com/
- Headers:
- Content-Type: application/json
- X-API-Key: your-secret-api-key-here
- Body: (same JSON-RPC format as before)


n8n Integration

Integrate this MCP server into your n8n workflows using the HTTP Request node.

HTTP Request Node Setup

  1. Add an HTTP Request node to your workflow

  2. Configure the node:

  • Method: POST
  • URL: https://your-domain.com/
  • Authentication: None (use headers for API key)
  1. Add Headers:
Name Value
Content-Type application/json
X-API-KEY your-api-key-here
  1. Set Body (JSON):json { "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "get_transcript", "arguments": { "url": "{{ $json.videoUrl }}", "language": "en" } } }

Example Workflow

Scenario: Extract transcript from YouTube URLs submitted via webhook

  1. Webhook Trigger - Receives YouTube URL
  2. HTTP Request - Calls this MCP server
  3. Set Node - Extracts transcript from response
  4. Process Transcript - Analyze, summarize, or store

Response Handling

The response will be in the result.structuredContent.transcript field:```javascript
// n8n expression to access transcript
{{ $json.result.structuredContent.transcript }}


---

## Configuration

### api_keys.json

Contains valid API keys for HTTP endpoint authentication.```json
{
  "keys": [
    "production-key-1",
    "production-key-2",
    "development-key"
  ]
}

docker-compose.yml

Configure environment variables:```yaml
version: '3.8'
services:
web:
build: .
ports:
- "5000:5000"
environment:
- AUTH_ENABLED=false # Set to 'false' to disable authentication


### Supported Languages

You can fetch transcripts in any language supported by YouTube. Common codes:

- `en` - English
- `fr` - French
- `es` - Spanish
- `de` - German
- `ja` - Japanese
- `ko` - Korean
- `zh` - Chinese
- `ar` - Arabic

**Example:**```bash
curl -H "X-API-KEY: your-key" \
  "http://localhost:5000/test_transcript?videoId=dQw4w9WgXcQ&lang=fr"

Troubleshooting

Docker Container Won't Start

Check logs:```bash
docker logs <container-name>


**Common issues:**
- Missing `api_keys.json` file
- Port 5000 already in use
- Invalid Docker configuration

### Claude Desktop Can&#x27;t Connect

**Verify:**
1. Server is accessible at the configured URL
2. Node.js and `npx` are available
3. `claude_desktop_config.json` syntax is correct
4. Claude Desktop has been fully restarted

**Test SSE endpoint:**```bash
curl https://your-domain.com/sse

n8n Returns 401 Unauthorized

Check:
1. X-API-KEY header is set correctly
2. API key exists in api_keys.json
3. AUTH_ENABLED is not set to false

Transcript Not Available

Possible causes:
- Video has no captions/subtitles
- Requested language not available
- Video is private or restricted
- yt-dlp needs updating

Solution: Try with lang=en (auto-generated English subtitles are most common)


License

This project is open source and available under the MIT License.


Contributing

Contributions are welcome! Please feel free to submit a Pull Request.


Acknowledgments

  • Built with FastMCP - Python MCP SDK
  • Uses yt-dlp for reliable transcript extraction
  • Implements the Model Context Protocol

常见问题

6 问
答案由本站依据条目字段整理,不引用上游原文
Youtube Transcript MCP Da293875 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Youtube Transcript MCP Da293875 怎么在 Claude Desktop、Claude 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Youtube Transcript MCP Da293875 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Youtube Transcript MCP Da293875 需要 API Key 吗?

资料标注需要API Key认证,使用前准备好对应凭据,并按最小权限配置。

Youtube Transcript MCP Da293875 支持哪些客户端?

资料标注支持 Claude Desktop、Claude;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Youtube Transcript MCP Da293875 能提供哪些能力?

资料显示能力标签包括 Python、Claude、AI代理。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。