Skip to main content
Glama
Sign In
Youtube138 MCP Server

Youtube138 MCP Server

by BACH-AI-Tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Youtube138 MCP Server

No user-submitted related servers found.

    Related Servers

    • videohub-port

      CloudCorpRecords
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching and retrieving YouTube videos, channels, playlists, comments and transcripts through the YouTube Data API v3 using an API key. Provides read-only tools for search, video and channel details, playlist items, comments, trending videos and plain-text caption transcripts.
      MIT

    • youtube-mcp-server

      BismaNwaz
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying YouTube Data API v3 through natural language, providing access to trending videos, search, channel uploads, video details, and comments.
      15 npm
      MIT

    • YouTube MCP Server

      OriShmila
      F
      license
      Not graded
      quality
      D
      maintenance
      Integrates with YouTube's Data API to enable video search, detailed video information retrieval, and transcript fetching with multi-language support and async performance.
      -
    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

    C2.1/5.0

    Scored across 20 tools

    Disambiguation3/5

    Most tools have distinct purposes targeting different YouTube resources (channels, videos, playlists, community posts), but there is notable overlap with 'channel_details' and 'channel_details_v2' which appear to be redundant versions, and 'search' and 'channel_search' could cause confusion about scope. The descriptions are clear enough to differentiate most tools, but the duplication and similar naming for search functions introduce ambiguity.

    Naming Consistency4/5

    The naming follows a consistent snake_case pattern with a clear resource_action structure (e.g., 'video_comments', 'playlist_details'), which is predictable and readable. However, there are minor deviations such as 'auto_complete' and 'home' that don't fit the pattern as neatly, and the use of 'v2' suffixes for some tools breaks consistency slightly.

    Tool Count3/5

    With 20 tools, the count is on the higher side for a YouTube API server, bordering on heavy but still manageable given the domain's complexity. It covers various aspects like channels, videos, playlists, and community features, but it might feel slightly bloated with redundant tools like the 'v2' versions, suggesting it could be streamlined without losing functionality.

    Completeness4/5

    The tool set provides comprehensive coverage for browsing and retrieving YouTube data, including channels, videos, playlists, community posts, comments, and search functionalities. Minor gaps exist, such as lack of tools for creating or modifying content (e.g., uploading videos or posting comments), but for a read-focused server, it covers the core viewing and discovery workflows well without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessSyncing

    Resources