Skip to main content
Glama
enesjakozh
williamvd4

YouTube Transcript Server

by williamvd4
OverviewSchemaRelated ServersScoreDiscussions
Remote

YouTubeトランスクリプトサーバー

鍛冶屋のバッジ

YouTube動画からトランスクリプトを取得できるモデルコンテキストプロトコルサーバーです。シンプルなインターフェースから動画のキャプションや字幕に直接アクセスできます。

Smithery経由でインストール

Smithery経由で Claude Desktop 用の YouTube Transcript Server を自動的にインストールするには:

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

素晴らしいMCPサーバー

awesome-mcp-servers素晴らしい Model Context Protocol (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. ビデオ URL でトランスクリプトを取得:

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ライセンスに基づいてライセンスされています。詳細はLICENSEファイルをご覧ください。

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