A
licenseB
qualityF
maintenanceEnables AI assistants to analyze and summarize YouTube videos by extracting captions, subtitles, and comprehensive metadata including title, description, and duration in multiple languages.
1
47 npm
62
MIT
Youtube MCP Server
by sparfenyuk
유튜브 MCP 서버
에 대한
이 서버는 Youtube API와 AI 어시스턴트를 연결하는 브리지 역할을 하며 Model Context Protocol을 기반으로 합니다.
Related MCP server: YouTube Tools MCP Server
MCP란 무엇인가요?
모델 컨텍스트 프로토콜(MCP)은 Claude Desktop과 같은 AI 앱이 외부 도구 및 데이터 소스에 연결할 수 있도록 하는 시스템입니다. AI 어시스턴트가 사용자의 제어권을 유지하면서 로컬 서비스 및 API를 사용할 수 있는 명확하고 안전한 방법을 제공합니다.
이 서버는 무슨 역할을 하나요?
[x] 주어진 비디오에 대한 닫힌 자막을 다운로드합니다.
실제 사용 사례
[x] 영상 요약을 작성하세요
필수 조건
설치
지엑스피1
[!NOTE] 이미 서버를 설치한 경우
uv tool upgrade --reinstall명령을 사용하여 업데이트할 수 있습니다.
[!NOTE] 서버를 삭제하려면
uv tool uninstall mcp-youtube명령을 사용하세요.
구성
클로드 데스크톱 구성
Claude Desktop이 Youtube MCP 서버를 인식하도록 구성합니다.
Claude Desktop 구성 파일을 엽니다.
MacOS에서는 구성 파일이
~/Library/Application Support/Claude/claude_desktop_config.json에 있습니다.Windows에서 구성 파일은
%APPDATA%\Claude\claude_desktop_config.json에 있습니다.
참고: Claude Desktop 앱 설정 내부에서도 claude_desktop_config.json을 찾을 수 있습니다.
서버 구성 추가
{ "mcpServers": { "mcp-youtube": { "command": "mcp-youtube", } } } }
개발
시작하기
저장소를 복제합니다
종속성을 설치하세요
uv sync서버를 실행하세요
uv run mcp-youtube --help
src/mcp_youtube/tools.py 파일에 도구를 추가할 수 있습니다.
새로운 도구를 추가하는 방법:
ToolArgs에서 상속되는 새 클래스를 만듭니다.
class NewTool(ToolArgs): """Description of the new tool.""" pass클래스의 속성은 도구의 인수로 사용됩니다. 클래스 docstring은 도구 설명으로 사용됩니다.
새 클래스에 대한 tool_runner 함수를 구현합니다.
@tool_runner.register async def new_tool(args: NewTool) -> t.Sequence[TextContent | ImageContent | EmbeddedResource]: pass이 함수는 TextContent, ImageContent 또는 EmbeddedResource의 시퀀스를 반환해야 합니다. 이 함수는 비동기적이어야 하며 새 클래스의 단일 인수를 받아야 합니다.
완료! 클라이언트를 다시 시작하면 새 도구를 사용할 수 있습니다.
검증은 Claude Desktop을 통해서나 도구를 직접 실행하여 수행할 수 있습니다.
Inspector에서 서버 디버깅
MCP 검사기는 멋진 UI를 사용하여 서버 디버깅을 지원하는 도구입니다. 실행하려면 다음 명령을 사용하세요.
npx @modelcontextprotocol/inspector uv run mcp-youtube문제 해결
'MCP 서버 mcp-youtube에 연결할 수 없습니다' 메시지
Claude Desktop에서 'MCP 서버 mcp-youtube에 연결할 수 없습니다'라는 메시지가 나타나면 서버 구성이 잘못되었다는 의미입니다.
다음을 시도해 보세요.
구성 파일에서
mcp-youtube바이너리의 전체 경로를 사용하세요.
Available Tools
1 toolDownloadClosedCaptionsC
Download closed captions from YouTube video.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| video_url | Yes |
TDQS
C2.8/5.0
Behavior2/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. While 'download' implies a read operation, it doesn't specify authentication requirements, rate limits, output format, error conditions, or whether it modifies any state. This leaves significant gaps in understanding 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 extremely concise at just one sentence with no wasted words. It's front-loaded with the core purpose and contains no unnecessary information.
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?
For a tool with no annotations, no output schema, and 0% schema description coverage, the description is insufficient. It doesn't explain what format the captions are returned in, whether authentication is needed, or any error handling. The minimal description leaves too many questions unanswered for effective use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema description coverage is 0%, and the description doesn't provide any information about the single parameter beyond what's implied by the tool name. No details about the video_url format, validation rules, or examples are given, leaving the parameter poorly documented.
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 action ('download') and resource ('closed captions from YouTube video'), making the purpose immediately understandable. However, with no sibling tools mentioned, there's no opportunity to differentiate from alternatives, which prevents a perfect score.
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 limitations. It simply states what the tool does without contextual usage information.
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 tool update
v1.0.0- Added
DownloadClosedCaptions
TDQS
C2.9/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no possibility of confusion or overlap between tools. The tool has a single, clear purpose that is distinct by default.
Naming Consistency5/5
The single tool name follows a clear verb_noun pattern (DownloadClosedCaptions), and with no other tools, consistency is inherently perfect. There are no deviations or mixed conventions to evaluate.
Tool Count2/5
A single tool for a YouTube server is too few for the apparent scope, as YouTube involves many operations like searching videos, getting metadata, or managing playlists. This feels thin and incomplete for the domain.
Completeness1/5
The tool surface is severely incomplete for a YouTube server. It only covers downloading closed captions, with no support for core YouTube functionalities such as video search, retrieval, or interaction, leading to significant gaps and agent failures.
Maintenance
ActivityInactive
ResponsivenessNo issues
Related MCP Connectors
YouTube transcripts, search, channel/playlist listings and upload tracking for AI agents.
Your YouTube library in Claude, ChatGPT and Cursor: transcripts, breakdowns, summaries, search.
Your YouTube library in Claude, ChatGPT and Cursor: transcripts, breakdowns, summaries, search.
Transcripts of YouTube videos, playlists and channels with timestamps; SRT or WebVTT too.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables AI assistants to search YouTube videos using the official YouTube Data API v3, extract full video transcripts in multiple languages, and store/retrieve video summaries using a local database.4MIT
- AlicenseAqualityAmaintenanceConnect AI assistants to YouTube: search, transcripts, metadata, and more.1964 npm6MIT
- AlicenseNot gradedqualityDmaintenanceExtracts captions, metadata, and descriptions from YouTube videos to enable AI assistants to summarize their content.8 npmMIT