YouTube Tools MCP Server
Related Servers
Alternatives to YouTube Tools MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to search videos, channels, and playlists, retrieve video metadata, transcripts, and comments via the YouTube Data API v3.46 PyPI68MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to search videos, read channels, browse playlists, fetch comments, and get transcripts from YouTube using the YouTube Data API v3 and InnerTube API for captions.2GPL 3.0
- AlicenseAqualityCmaintenanceEnables AI assistants to fetch YouTube transcripts with timestamps, search within a video, and keep a local searchable memory of every transcript fetched.4MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to search YouTube, fetch transcripts, and get AI summaries of videos without API keys.36 npmMIT
- AlicenseAqualityDmaintenanceEnables AI tools to access YouTube content, including transcript extraction, video/channel info, and search.423 npmMIT
- FlicenseBqualityDmaintenanceEnables interaction with YouTube through search and transcript extraction functionality. Allows searching for videos and retrieving full transcripts with timestamps for content analysis.28-
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: searching YouTube, fetching transcripts, and retrieving/storing summaries. There is no overlap between tool responsibilities, so an agent can easily select the correct tool for a task.
The tool names mix conventions: 'get_youtube_transcript' and 'search_youtube' use snake_case and include 'youtube', while 'fetchExistingVideoSummary' and 'storeVideoSummary' use camelCase and omit the service name. The inconsistent verb choices (get vs fetch, store vs search) further reduce predictability.
With only 4 tools, the server is tightly scoped to its purpose of YouTube video search, transcript retrieval, and summary management. Each tool is necessary and there is no bloat, making the count appropriate for the domain.
The tool set covers the core workflows: search, transcript, and summary storage/retrieval. A delete summary tool is missing, but the store operation handles both create and update, so the surface is largely complete for the implied use case.