Skip to main content
Glama
enesjakozh
williamvd4

YouTube Transcript Server

by williamvd4
OverviewSchemaRelated ServersScoreDiscussions
Remote

YouTube 转录服务器

铁匠徽章

一个模型上下文协议服务器，支持检索 YouTube 视频的文字记录。该服务器通过简单的界面直接访问视频字幕。

通过 Smithery 安装

要通过Smithery自动为 Claude Desktop 安装 YouTube 成绩单服务器：

npx -y @smithery/cli install @kimtaeyoon83/mcp-server-youtube-transcript --client claude

成分

工具

  • 获取成绩单

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

    • 输入：

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

      • lang （字符串，可选，默认值：“en”）：成绩单的语言代码（例如，'ko'，'en'）

Related MCP server: YouTube Transcript Extractor MCP

主要特点

  • 支持多种视频 URL 格式

  • 特定语言的成绩单检索

  • 响应中的详细元数据

配置

要与 Claude Desktop 一起使用，请添加此服务器配置：

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

通过工具安装

mcp-get用于安装和管理模型上下文协议 (MCP) 服务器的命令行工具。

npx @michaellatman/mcp-get@latest install @kimtaeyoon83/mcp-server-youtube-transcript

Awesome-mcp-服务器

awesome-mcp-servers精选的优秀模型上下文协议 (MCP) 服务器列表。

发展

先决条件

  • Node.js 18 或更高版本

  • npm 或 yarn

设置

安装依赖项：

npm install

构建服务器：

npm run build

对于使用自动重建的开发：

npm run watch

测试

npm test

调试

由于 MCP 服务器通过 stdio 进行通信，调试起来可能比较困难。我们建议使用 MCP Inspector 进行开发：

npm run inspector

错误处理

服务器针对常见场景实现了强大的错误处理：

  • 视频 URL 或 ID 无效

  • 无法获取成绩单

  • 语言可用性问题

  • 网络错误

使用示例

  1. 通过视频网址获取成绩单：

await server.callTool("get_transcript", {
  url: "https://www.youtube.com/watch?v=VIDEO_ID",
  lang: "en"
});

  1. 通过视频ID获取成绩单：

await server.callTool("get_transcript", {
  url: "VIDEO_ID",
  lang: "ko"
});

  1. 如何在 Claude 桌面应用程序中提取 YouTube 字幕

chat: https://youtu.be/ODaHJzOyVCQ?si=aXkJgso96Deri0aB Extract subtitles

安全注意事项

服务器：

  • 验证所有输入参数

  • 优雅地处理 YouTube API 错误

  • 实现成绩单检索超时

  • 提供详细的错误消息以进行故障排除

执照

此 MCP 服务器采用 MIT 许可证。详情请参阅许可证文件。

Available Tools

1 tool
get_transcriptC

Extract transcript from a YouTube video URL or ID

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYesYouTube video URL or ID
langYesLanguage code for transcript (e.g., 'ko', 'en')en

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions extraction but doesn't disclose behavioral traits like rate limits, authentication needs, error handling, or what happens if the video lacks a transcript. This leaves significant gaps for an agent to understand the tool's behavior.

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

Conciseness5/5

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

The description is a single, efficient sentence that directly states the tool's purpose without any wasted words. It is appropriately sized and front-loaded, making it easy to parse.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain return values, error cases, or operational constraints, which are crucial for a tool that interacts with external services like YouTube. This leaves the agent with insufficient context for effective use.

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?

The description implies parameters for URL/ID and language, but the input schema already has 100% coverage with clear descriptions for 'url' and 'lang'. The description adds minimal value beyond the schema, so it meets the baseline of 3 for high schema coverage.

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

Purpose4/5

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

The description clearly states the verb 'extract' and the resource 'transcript from a YouTube video', making the purpose specific and understandable. However, with no sibling tools mentioned, it cannot differentiate from alternatives, so it doesn't reach the highest score of 5.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or exclusions. It only states what the tool does, with no context for usage decisions.

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. Dates show when Glama detected each change.

  1. 1 tool update
    • First observedget_transcript
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.1/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as extracting transcripts from YouTube videos, making it distinct by default.

Naming Consistency5/5

The single tool name follows a clear verb_noun pattern (get_transcript), which is consistent and predictable. There are no other tools to compare against, so no inconsistency can exist.

Tool Count2/5

A single tool is too few for a server that might be expected to handle YouTube transcripts comprehensively. While it covers extraction, there are likely gaps such as searching transcripts, handling errors, or managing multiple videos, making the scope feel thin and incomplete.

Completeness2/5

The server is severely incomplete for a YouTube transcript domain. It only provides extraction, missing obvious operations like searching within transcripts, listing available transcripts, or handling transcript formats (e.g., timestamps, languages), which are common needs in this context.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/williamvd4/mcp-server-youtube-transcript'

If you have feedback or need assistance with the MCP directory API, please join our Discord server