Eine Model Context Protocol (MCP)-Serverimplementierung für YouTube, die es KI-Sprachmodellen ermöglicht, über eine standardisierte Schnittstelle mit YouTube-Inhalten zu interagieren.
Erhalten Sie Videodetails (Titel, Beschreibung, Dauer usw.)
Kanalvideos auflisten
Erhalten Sie Videostatistiken (Aufrufe, Likes, Kommentare)
Suchen Sie auf YouTube nach Videos
Videotranskripte abrufen
Unterstützung für mehrere Sprachen
Erhalten Sie Untertitel mit Zeitstempel
Suche in Transkripten
Kanaldetails abrufen
Kanal-Wiedergabelisten auflisten
Kanalstatistiken abrufen
Suche innerhalb des Kanalinhalts
Auflisten von Wiedergabelistenelementen
Details zur Wiedergabeliste abrufen
Suche innerhalb von Wiedergabelisten
Holen Sie sich die Transkripte der Playlist-Videos
Related MCP server: mcp-youtube-transcript
So installieren Sie den YouTube MCP-Server für Claude Desktop automatisch über Smithery :
npx -y @smithery/cli install @ZubeidHendricks/youtube --client claudenpm install zubeid-youtube-mcp-serverLegen Sie die folgenden Umgebungsvariablen fest:
YOUTUBE_API_KEY : Ihr YouTube-Daten-API-Schlüssel
YOUTUBE_TRANSCRIPT_LANG : Standardsprache für Transkripte (optional, standardmäßig „en“)
Fügen Sie dies zu Ihrer MCP-Clientkonfiguration hinzu (z. B. Claude Desktop):
{
"mcpServers": {
"youtube": {
"command": "npx",
"args": ["-y", "zubeid-youtube-mcp-server"],
"env": {
"YOUTUBE_API_KEY": "<YOUR_API_KEY>"
}
}
}
}Klicken Sie für die Ein-Klick-Installation auf eine der folgenden Installationsschaltflächen:
Wenn Sie die manuelle Installation bevorzugen, aktivieren Sie zunächst die Installationsschaltflächen oben in diesem Abschnitt. Andernfalls gehen Sie folgendermaßen vor:
Fügen Sie den folgenden JSON-Block zu Ihrer Benutzereinstellungsdatei (JSON) in VS Code hinzu. Drücken Sie dazu Ctrl + Shift + P und geben Sie Preferences: Open User Settings (JSON) ein.
{
"mcp": {
"inputs": [
{
"type": "promptString",
"id": "apiKey",
"description": "YouTube API Key",
"password": true
}
],
"servers": {
"youtube": {
"command": "npx",
"args": ["-y", "zubeid-youtube-mcp-server"],
"env": {
"YOUTUBE_API_KEY": "${input:apiKey}"
}
}
}
}
}Optional können Sie es zu einer Datei namens .vscode/mcp.json in Ihrem Arbeitsbereich hinzufügen:
{
"inputs": [
{
"type": "promptString",
"id": "apiKey",
"description": "YouTube API Key",
"password": true
}
],
"servers": {
"youtube": {
"command": "npx",
"args": ["-y", "zubeid-youtube-mcp-server"],
"env": {
"YOUTUBE_API_KEY": "${input:apiKey}"
}
}
}
}Gehen Sie zur Google Cloud Console
Erstellen Sie ein neues Projekt oder wählen Sie ein vorhandenes aus
Aktivieren Sie die YouTube Data API v3
API-Anmeldeinformationen (API-Schlüssel) erstellen
Kopieren Sie den API-Schlüssel zur Konfiguration
// Get video details
const video = await youtube.videos.getVideo({
videoId: "video-id"
});
// Get video transcript
const transcript = await youtube.transcripts.getTranscript({
videoId: "video-id",
language: "en"
});
// Search videos
const searchResults = await youtube.videos.searchVideos({
query: "search term",
maxResults: 10
});// Get channel details
const channel = await youtube.channels.getChannel({
channelId: "channel-id"
});
// List channel videos
const videos = await youtube.channels.listVideos({
channelId: "channel-id",
maxResults: 50
});// Get playlist items
const playlistItems = await youtube.playlists.getPlaylistItems({
playlistId: "playlist-id",
maxResults: 50
});
// Get playlist details
const playlist = await youtube.playlists.getPlaylist({
playlistId: "playlist-id"
});# Install dependencies
npm install
# Run tests
npm test
# Build
npm run build
# Lint
npm run lintInformationen zum Mitwirken an diesem Repository finden Sie unter CONTRIBUTING.md.
Dieses Projekt ist unter der MIT-Lizenz lizenziert – Einzelheiten finden Sie in der Datei LICENSE.
Search for videos on YouTube
| Name | Required | Description | Default |
|---|---|---|---|
| order | No | Sort order for results, such as relevance or date | |
| query | Yes | Search query | |
| sortBy | No | Optional ranking mode such as relevance, indie_priority, subscribers_asc, subscribers_desc, or recent_activity | |
| channelId | No | Restrict results to a specific channel ID | |
| maxResults | No | Maximum number of results to return | |
| creatorOnly | No | Only include channels heuristically classified as creators | |
| publishedAfter | No | Only include videos published after this ISO 8601 date | |
| uniqueChannels | No | Return only one matched video per unique channel | |
| publishedBefore | No | Only include videos published before this ISO 8601 date | |
| channelMaxSubscribers | No | Maximum subscriber count for the matched video channel | |
| channelMinSubscribers | No | Minimum subscriber count for the matched video channel | |
| channelLastUploadAfter | No | Only include videos whose channel latest upload is after this ISO 8601 date | |
| channelLastUploadBefore | No | Only include videos whose channel latest upload is before this ISO 8601 date |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
There are no annotations, so the description must disclose behavioral traits. It only says 'Search for videos,' omitting any details about rate limits, pagination, return format, or side effects. This is insufficient for an agent to anticipate behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence, which is too brief for a tool with 13 parameters. While concise, it is under-specified and does not earn its place; it should include more context.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (13 parameters, no output schema), the description lacks completeness. It does not explain return values, default behaviors, or interaction effects between parameters, leaving the agent underinformed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage, so the schema itself documents each parameter. The tool description adds no additional meaning beyond the schema, making the baseline score of 3 appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states a specific verb ('Search') and resource ('videos on YouTube'), making the tool's purpose immediately understandable. However, it lacks any differentiation from potential sibling tools (none provided) and is somewhat generic.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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, when not to use it, or any alternatives. With no sibling tools mentioned, the description could at least imply typical search scenarios, but it does not.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.0.2channels_getChannelchannels_listVideosplaylists_getPlaylistplaylists_getPlaylistItemstranscripts_getTranscriptvideos_getVideovideos_searchVideos11 fields changedInput schema / properties / channelIdAdded value: +{
+ "description": "Restrict results to a specific channel ID",
+ "type": "string"
+}Input schema / properties / channelLastUploadAfterAdded value: +{
+ "description": "Only include videos whose channel latest upload is after this ISO 8601 date",
+ "type": "string"
+}Input schema / properties / channelLastUploadBeforeAdded value: +{
+ "description": "Only include videos whose channel latest upload is before this ISO 8601 date",
+ "type": "string"
+}Input schema / properties / channelMaxSubscribersAdded value: +{
+ "description": "Maximum subscriber count for the matched video channel",
+ "type": "number"
+}Input schema / properties / channelMinSubscribersAdded value: +{
+ "description": "Minimum subscriber count for the matched video channel",
+ "type": "number"
+}Input schema / properties / creatorOnlyAdded value: +{
+ "description": "Only include channels heuristically classified as creators",
+ "type": "boolean"
+}Input schema / properties / orderAdded value: +{
+ "description": "Sort order for results, such as relevance or date",
+ "type": "string"
+}Input schema / properties / publishedAfterAdded value: +{
+ "description": "Only include videos published after this ISO 8601 date",
+ "type": "string"
+}Input schema / properties / publishedBeforeAdded value: +{
+ "description": "Only include videos published before this ISO 8601 date",
+ "type": "string"
+}Input schema / properties / sortByAdded value: +{
+ "description": "Optional ranking mode such as relevance, indie_priority, subscribers_asc, subscribers_desc, or recent_activity",
+ "type": "string"
+}Input schema / properties / uniqueChannelsAdded value: +{
+ "description": "Return only one matched video per unique channel",
+ "type": "boolean"
+}v1.0.0channels_getChannelchannels_listVideosplaylists_getPlaylistplaylists_getPlaylistItemstranscripts_getTranscriptvideos_getVideovideos_searchVideosScored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools, so disambiguation is perfect.
The single tool name 'videos_searchVideos' mixes camelCase and an awkward verb_noun structure ('videos' as prefix then 'searchVideos'), showing internal inconsistency and lack of a clear pattern.
One tool is far too few for a YouTube MCP server, which typically requires multiple operations (search, video details, channel info, etc.), making the tool count extremely inadequate.
The tool only supports searching for videos, missing critical operations like retrieving video details, listing playlists, or managing subscriptions, leaving severe gaps in covering the YouTube domain.
YouTube transcripts, search, channel/playlist listings and upload tracking for AI agents.
YouTube transcripts, search, and channel and playlist listings for any AI app. Hosted.
YouTube transcripts, search, channel browsing, and playlists for AI agents via MCP.
YouTube for AI agents: transcripts, comments, video stats, channel monitor, Shorts captions.
