Una implementación de servidor de Protocolo de contexto de modelo (MCP) para YouTube, que permite que los modelos de lenguaje de IA interactúen con el contenido de YouTube a través de una interfaz estandarizada.
Obtenga detalles del video (título, descripción, duración, etc.)
Lista de vídeos del canal
Obtener estadísticas de vídeo (visualizaciones, me gusta, comentarios)
Buscar vídeos en YouTube
Recuperar transcripciones de vídeo
Soporte para múltiples idiomas
Obtener subtítulos con marca de tiempo
Buscar dentro de las transcripciones
Obtener detalles del canal
Lista de reproducción de canales
Obtener estadísticas del canal
Buscar dentro del contenido del canal
Lista de elementos de la lista de reproducción
Obtener detalles de la lista de reproducción
Buscar dentro de las listas de reproducción
Obtener transcripciones de videos de listas de reproducción
Related MCP server: mcp-youtube-transcript
Para instalar YouTube MCP Server para Claude Desktop automáticamente a través de Smithery :
npx -y @smithery/cli install @ZubeidHendricks/youtube --client claudenpm install zubeid-youtube-mcp-serverEstablezca las siguientes variables de entorno:
YOUTUBE_API_KEY : Su clave de API de datos de YouTube
YOUTUBE_TRANSCRIPT_LANG : idioma predeterminado para las transcripciones (opcional, el valor predeterminado es 'en')
Agregue esto a la configuración de su cliente MCP (por ejemplo, Claude Desktop):
{
"mcpServers": {
"youtube": {
"command": "npx",
"args": ["-y", "zubeid-youtube-mcp-server"],
"env": {
"YOUTUBE_API_KEY": "<YOUR_API_KEY>"
}
}
}
}Para la instalación con un solo clic, haga clic en uno de los botones de instalación a continuación:
Si prefiere la instalación manual, primero revise los botones de instalación en la parte superior de esta sección. De lo contrario, siga estos pasos:
Agrega el siguiente bloque JSON a tu archivo de configuración de usuario (JSON) en VS Code. Para ello, presiona Ctrl + Shift + P y escribe Preferences: Open User Settings (JSON) .
{
"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}"
}
}
}
}
}Opcionalmente, puede agregarlo a un archivo llamado .vscode/mcp.json en su espacio de trabajo:
{
"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}"
}
}
}
}Ir a la consola de Google Cloud
Crea un nuevo proyecto o selecciona uno existente
Habilitar la API de datos de YouTube v3
Crear credenciales de API (clave API)
Copiar la clave API para la configuración
// 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 lintConsulte CONTRIBUTING.md para obtener información sobre cómo contribuir a este repositorio.
Este proyecto está licenciado bajo la licencia MIT: consulte el archivo de LICENCIA para obtener más detalles.
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.
Transcripts, translations, summaries, subtitles, and search for public YouTube videos.
