Skip to main content
Glama
Unknowmyt1M

YouTube Research MCP

by Unknowmyt1M
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to YouTube Research MCP

No user-submitted related servers found.

    Related Servers

    • tubescout

      not0lucky
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to search YouTube like a database, retrieve transcripts and channel data, and mine videos for claims, numbers, and demand signals — without needing an API key.
      6
      34 npm
      MIT

    • VidLens

      thatsrajan
      A
      license
      C
      quality
      B
      maintenance
      Enables AI agents to search, analyze, and extract insights from YouTube videos including transcripts, visual frames, and benchmarks without requiring API keys. Supports semantic search across playlists, sentiment analysis, and visual content indexing with automatic fallback chains for reliable access.
      41
      162 npm
      35
      MIT

    • @kirbah/mcp-youtube

      Aj-Niplex
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides AI agents with token-optimized access to YouTube data, including video details, transcripts, channel statistics, trending videos, and search.
      1,088 npm
      MIT

    • youtube-signal-mcp

      alibabagini-cyber
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to retrieve YouTube transcripts, video info, channel video lists, and monitor channels for new uploads, with built-in prompt templates for summaries and industry signals—all without an API key.
      4
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 5 tools

    Disambiguation4/5

    The tools mostly target distinct actions: metadata retrieval, search, transcript extraction, pinpointing content, and autonomous research. The only potential confusion is between youtube_search (finding videos) and youtube_research (which also discovers videos), but the descriptions clarify that youtube_research is a higher-level aggregation tool that subsumes search and transcript extraction.

    Naming Consistency3/5

    All tools share the 'youtube_' prefix, which is consistent, but the suffixes mix nouns (video, transcript, research) with verbs (search, find_in_video). This is not a strict verb_noun pattern like the calibration example. The inconsistency is minor but noticeable; a more uniform pattern like youtube_get_video, youtube_search_videos, etc., would improve coherence.

    Tool Count5/5

    With 5 tools, the count is well within the ideal 3-15 range. Each tool serves a distinct purpose in the research workflow (discovery, metadata, transcript, semantic search, aggregation), and none feels redundant. The number is appropriate for the server's stated purpose.

    Completeness4/5

    The tool surface covers the core research lifecycle: search, inspect (metadata), extract (transcript), locate (find_in_video), and synthesize (research). Minor gaps exist, such as no tool for channel-specific queries or playlist retrieval, but these are not essential for the primary research workflow. The inclusion of caption availability checks and language provenance shows attention to detail.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources