tube-bridge
Related Servers
Alternatives to tube-bridge
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server that provides YouTube video data to AI agents, supporting search, metadata, comments, and transcripts without an API key.510 npmMIT
- AlicenseNot gradedqualityNot gradedmaintenanceAn MCP server that provides YouTube data access without API keys or quotas. It enables agents to search videos, retrieve transcripts and metadata, and perform full-text search across cached content for AI context retrieval.3 npm-
- AlicenseNot gradedqualityCmaintenanceA comprehensive MCP server providing YouTube transcript retrieval, video search, channel browsing, playlist extraction, and upload monitoring for AI agents.10MIT
- AlicenseAqualityDmaintenanceMCP server that lets AI agents search YouTube and fetch transcripts.2102 PyPI3MIT
- AlicenseBqualityDmaintenanceAn MCP server that provides AI assistants with powerful tools to interact with YouTube, including video searching, transcript extraction, comment retrieval, and more.819Apache 2.0
- FlicenseNot gradedqualityDmaintenanceMCP server for YouTube that provides tools to fetch video metadata and transcripts, enabling natural language queries about YouTube videos.2-
TDQS
Scored across 17 tools
Every tool addresses a distinct resource or action: searching channels vs. videos, fetching channel metadata vs. channel uploads, video metadata vs. transcript vs. comments vs. frames, and clear corpus operations. Even similar-looking tools like youtube_get_channel_info and youtube_get_channel_videos are unambiguous due to explicit descriptions.
Most tools follow a predictable pattern: youtube_<verb>_<resource> or corpus_<verb>. Minor deviations include youtube_get_trending (no resource noun) and tube_bridge_help (namespace mismatch), but the overall structure remains readable and consistent.
With 17 tools covering YouTube data retrieval, transcript processing, and semantic corpus management, the count is slightly high but justified by the broad scope. Each tool has a clear purpose, and the split between YouTube-facing and corpus-facing tools keeps the set manageable.
The tool set covers the full YouTube read-only surface: search, channel/video/playlist metadata, transcripts, frames, languages, comments, and trending. Corpus tools provide create/add/search/list/delete, and force_reembed covers updates. The help tool fills documentation gaps, so no critical operations are missing.