Skip to main content
Glama
enesjakozh
sinco-lab

mcp-youtube-transcript

by sinco-lab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

MCP YouTube 转录服务器

铁匠徽章

一个模型上下文协议服务器，支持检索 YouTube 视频的文字记录。该服务器通过简单的界面直接访问视频文字记录，非常适合内容分析和处理。

目录

Related MCP server: YouTube Transcript Server

特征

✨ 主要功能：

  • 从 YouTube 视频中提取文字记录

  • 支持多种语言

  • 使用连续或段落模式格式化文本

  • 检索视频标题和元数据

  • 自动段落分割

  • 文本规范化和 HTML 实体解码

  • 强大的错误处理

  • 时间戳和重叠检测

入门

先决条件

  • Node.js 18 或更高版本

安装

我们提供两种安装方法：

选项 1：手动配置（推荐用于生产）

  1. 创建或编辑 Claude Desktop 配置文件：

    • macOS： ~/Library/Application Support/Claude/claude_desktop_config.json

    • Windows： %APPDATA%\Claude\claude_desktop_config.json

  2. 添加以下配置：

{
  "mcpServers": {
    "youtube-transcript": {
      "command": "npx",
      "args": [
        "-y",
        "@sinco-lab/mcp-youtube-transcript"
      ]
    }
  }
}

macOS 的快速安装脚本：

# Create directory if it doesn't exist
mkdir -p ~/Library/Application\ Support/Claude

# Create or update config file
cat > ~/Library/Application\ Support/Claude/claude_desktop_config.json << 'EOL'
{
  "mcpServers": {
    "youtube-transcript": {
      "command": "npx",
      "args": [
        "-y",
        "@sinco-lab/mcp-youtube-transcript"
      ]
    }
  }
}
EOL

选项 2：通过 Smithery（仅限开发）

npx -y @smithery/cli install @sinco-lab/mcp-youtube-transcript --client claude

⚠️注意：不建议将此方法用于生产，因为它依赖于 Smithery 的代理服务。

用法

基本配置

要与 Claude Desktop / Cursor / cline 一起使用，请确保您的配置匹配：

{
  "mcpServers": {
    "youtube-transcript": {
      "command": "npx",
      "args": ["-y", "@sinco-lab/mcp-youtube-transcript"]
    }
  }
}

测试

与克劳德·阿普

  1. 安装后重新启动 Claude 应用程序

  2. 使用简单命令进行测试：

    https://www.youtube.com/watch?v=AJpK3YTTKZ4 Summarize this video

示例输出：演示

使用 MCP 检查器

# Clone and setup
git clone https://github.com/sinco-lab/mcp-youtube-transcript.git
cd mcp-youtube-transcript
npm install
npm run build

# Launch inspector
npx @modelcontextprotocol/inspector node "dist/index.js"

# Access http://localhost:6274 and try these commands:
# 1. List Tools: clink `List Tools`
# 2. Test get_transcripts with:
#    url: "https://www.youtube.com/watch?v=AJpK3YTTKZ4"
#    lang: "en" (optional)
#    enableParagraphs: false (optional)

故障排除和维护

检查克劳德日志

要监控Claude的日志，可以使用以下命令：

tail -n 20 -f ~/Library/Logs/Claude/mcp*.log

这将显示日志文件的最后 20 行，并在添加新条目时继续显示它们。

注意：Claude 应用程序会自动为 MCP 服务器日志文件添加mcp-server-前缀。例如，我们服务器的日志将被写入mcp-server-youtube-transcript.log 。

清理npx缓存

如果您遇到与npx缓存相关的问题，您可以使用以下方法手动清理它：

rm -rf ~/.npm/_npx

这将删除缓存的包并允许您重新开始。

API 参考

获取成绩单

从 YouTube 视频中获取文字记录。

参数：

  • url （字符串，必需）：YouTube 视频 URL 或 ID

  • lang （字符串，可选）：语言代码（默认值：“en”）

  • enableParagraphs （布尔值，可选）：启用段落模式（默认值：false）

响应格式：

{
  "content": [{
    "type": "text",
    "text": "Video title and transcript content",
    "metadata": {
      "videoId": "video_id",
      "title": "video_title",
      "language": "transcript_language",
      "timestamp": "processing_time",
      "charCount": "character_count",
      "transcriptCount": "number_of_transcripts",
      "totalDuration": "total_duration",
      "paragraphsEnabled": "paragraph_mode_status"
    }
  }]
}

发展

项目结构

├── src/
│ ├── index.ts            # Server entry point
│ ├── youtube.ts          # YouTube transcript fetching logic
├── dist/                 # Compiled output
└── package.json

关键组件

  • YouTubeTranscriptFetcher ：核心成绩单获取功能

  • YouTubeUtils ：文本处理和实用程序

特性和功能

  • 错误处理：

    • 无效的 URL/ID

    • 无法获取成绩单

    • 语言可用性

    • 网络错误

    • 速率限制

  • 文本处理：

    • HTML实体解码

    • 标点规范化

    • 空间规范化

    • 智能段落检测

贡献

欢迎大家贡献！欢迎随时提交问题和拉取请求。

执照

该项目根据 MIT 许可证获得许可 - 有关详细信息，请参阅LICENSE文件。

相关项目

Available Tools

1 tool
get_transcriptsA

Extract and process transcripts from a YouTube video.

Parameters:

  • url (string, required): YouTube video URL or ID.

  • lang (string, optional, default 'en'): Language code for transcripts (e.g. 'en', 'uk', 'ja', 'ru', 'zh').

  • enableParagraphs (boolean, optional, default false): Enable automatic paragraph breaks.

IMPORTANT: If the user does not specify a language code, DO NOT include the lang parameter in the tool call. Do not guess the language or use parts of the user query as the language code.

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYesYouTube video URL or ID
langNoLanguage code for transcripts, default 'en' (e.g. 'en', 'uk', 'ja', 'ru', 'zh')en
enableParagraphsNoEnable automatic paragraph breaks, default `false`

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively explains the tool's core function and includes important behavioral guidance about parameter handling (the IMPORTANT note about not guessing language). However, it doesn't mention potential limitations like video availability, transcript existence, rate limits, or error conditions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a clear purpose statement followed by parameter documentation and important usage notes. Every sentence serves a purpose, though the parameter list slightly duplicates schema information. The IMPORTANT section is appropriately emphasized for critical behavioral guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations and no output schema, the description provides adequate coverage for the tool's basic function and parameters. However, it lacks information about return values, error handling, and operational constraints that would be helpful for an agent. The IMPORTANT note adds valuable context, but more behavioral transparency would improve completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description repeats this information in a bulleted list without adding significant semantic context beyond what's in the schema. The IMPORTANT note about language parameter handling adds some value, but overall the description doesn't enhance parameter understanding beyond the structured schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with specific verbs ('extract and process') and resource ('transcripts from a YouTube video'). It distinguishes itself from potential alternatives by focusing on transcript extraction rather than other video-related operations, though no sibling tools exist for direct comparison.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides some usage guidance through the IMPORTANT note about language parameter handling, but it doesn't explicitly state when to use this tool versus alternatives (e.g., when transcripts are needed vs. other video metadata). Since no sibling tools exist, this is less critical, but general context about appropriate use cases is missing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • First observedget_transcripts
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.7/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.

Naming Consistency5/5

Since there is only one tool, naming consistency is inherently perfect. The tool name 'get_transcripts' follows a clear verb_noun pattern.

Tool Count2/5

A single tool is too few for a server focused on YouTube transcripts, as it lacks operations like searching transcripts, managing multiple videos, or handling errors. This minimal scope limits functionality and agent workflows.

Completeness2/5

The tool set is severely incomplete for the domain of YouTube transcript processing. It only provides extraction (get_transcripts), missing essential operations such as searching within transcripts, listing available languages, or handling video metadata, which are common needs in this context.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches