Skip to main content
Glama
bigbatmanorg

YouTube Personal Playlist noAPI MCP

by bigbatmanorg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to YouTube Personal Playlist noAPI MCP

No user-submitted related servers found.

    Related Servers

    • ytmusic-mcp

      ShinoharaTa
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables natural-language management of a YouTube Music account, including playlist creation and editing, song search, ratings, and library organization through a local MCP server.
      -

    • yt-playlist-organizer-mcp

      Thib-ai
      A
      license
      A
      quality
      C
      maintenance
      An MCP server for organizing YouTube playlists via the YouTube Data API v3, enabling playlist and playlist item creation, listing, updating, and deletion through natural language.
      9
      MIT

    • yt-curator-mcp

      GeniusTechnoMystic
      A
      license
      A
      quality
      B
      maintenance
      Enables YouTube playlist curation including inventory, deduplication, merging, and deletion via MCP tools.
      12
      MIT

    • YT Music Manager

      Robin-Kurian
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding tools and MCP hosts to search YouTube Music and add or remove tracks on your own playlists through natural-language prompts, authenticated with your Google login. It runs locally over stdio, so credentials and OAuth tokens stay on your machine.
      -

    • YouTube MCP Connector

      deepujain
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-compatible clients to search YouTube videos, read subscriptions and playlists, generate catch-up digests of recent uploads, and manage playlists with approval-gated writes via the YouTube Data API v3.
      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

    B3.3/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool targets a distinct operation: cookie management (set/status), account info, playlist listing/retrieval, and playlist mutations (create/delete/rename/description/video add/remove). There is no overlap that would cause an agent to select the wrong tool; even similar-sounding tools like rename_playlist and set_playlist_description are clearly differentiated by their descriptions.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern with a consistent 'youtube_' prefix (e.g., youtube_list_playlists, youtube_get_playlist, youtube_create_playlist). However, three tools deviate: youtube_cookie_set and youtube_cookie_status use a noun_verb/noun_noun structure, and youtube_account_info is noun_noun. These are minor deviations that remain readable and predictable.

    Tool Count5/5

    With 11 tools, the set is well-scoped for managing YouTube playlists without an API. It covers authentication, account info, playlist CRUD, and video membership without excessive redundancy. Each tool earns its place and the count is comfortably within the 3–15 ideal range.

    Completeness4/5

    The surface covers the core playlist lifecycle: authentication, listing, reading, creating, deleting, renaming, setting descriptions, and adding/removing videos. Minor gaps exist, such as tools for reordering or moving videos within a playlist, but these are non-essential for most workflows and can be worked around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources