Skip to main content
Glama
enesjakozh
williamvd4

YouTube Transcript Server

by williamvd4
OverviewSchemaRelated ServersScoreDiscussions
Remote

Servidor de transcripciones de YouTube

insignia de herrería

Un servidor de Protocolo de Contexto de Modelo que permite la recuperación de transcripciones de vídeos de YouTube. Este servidor proporciona acceso directo a los subtítulos de los vídeos mediante una interfaz sencilla.

Instalación mediante herrería

Para instalar YouTube Transcript Server para Claude Desktop automáticamente a través de Smithery :

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

Componentes

Herramientas

  • obtener_transcripción

    • Extraer transcripciones de vídeos de YouTube

    • Entradas:

      • url (cadena, obligatoria): URL del vídeo de YouTube o ID del vídeo

      • lang (cadena, opcional, valor predeterminado: "en"): Código de idioma para la transcripción (por ejemplo, 'ko', 'en')

Related MCP server: YouTube Transcript Extractor MCP

Características principales

  • Compatibilidad con múltiples formatos de URL de vídeo

  • Recuperación de transcripciones específicas del idioma

  • Metadatos detallados en las respuestas

Configuración

Para usar con Claude Desktop, agregue esta configuración de servidor:

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

Instalar mediante herramienta

mcp-get Una herramienta de línea de comandos para instalar y administrar servidores de Protocolo de contexto de modelo (MCP).

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

Servidores Awesome-mcp

awesome-mcp-servers Una lista seleccionada de increíbles servidores de Protocolo de Contexto de Modelo (MCP).

Desarrollo

Prerrequisitos

  • Node.js 18 o superior

  • npm o hilo

Configuración

Instalar dependencias:

npm install

Construir el servidor:

npm run build

Para desarrollo con reconstrucción automática:

npm run watch

Pruebas

npm test

Depuración

Dado que los servidores MCP se comunican a través de stdio, la depuración puede ser complicada. Recomendamos usar el Inspector MCP para el desarrollo:

npm run inspector

Manejo de errores

El servidor implementa un manejo robusto de errores para escenarios comunes:

  • URL o ID de vídeo no válidos

  • Transcripciones no disponibles

  • Problemas de disponibilidad del idioma

  • Errores de red

Ejemplos de uso

  1. Obtener la transcripción por URL del video:

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

  1. Obtener transcripción por ID de video:

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

  1. Cómo extraer subtítulos de YouTube en la aplicación de escritorio Claude

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

Consideraciones de seguridad

El servidor:

  • Valida todos los parámetros de entrada

  • Maneja los errores de la API de YouTube con elegancia

  • Implementa tiempos de espera para la recuperación de transcripciones

  • Proporciona mensajes de error detallados para la solución de problemas.

Licencia

Este servidor MCP está licenciado bajo la licencia MIT. Consulte el archivo de licencia para obtener más información.

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