Add MCP server: GetYouTubeTranscript (remote, YouTube transcripts and search)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 62/100
Research direction
Read the registry inclusion heuristics and management documentation linked in the issue, then inspect existing remote server entries in the catalog. If the server meets the review criteria, add a remote server entry for GetYouTubeTranscript that references this issue; done when the entry follows the catalog format and is ready for review.
Written by the indexing model from the issue text.
Description
MCP Server Information
Server Name: GetYouTubeTranscript (YouTube transcripts and YouTube search)
Repository URL: https://github.com/tubeagentkit/youtube-mcp
Brief Description: Official remote MCP server for getyoutubetranscript.com (streamable HTTP at https://getyoutubetranscript.com/api/mcp). Tools: YouTube video transcripts in any caption language a video has (get_youtube_transcript, get_transcript_languages), YouTube search, channel videos/playlists/posts, related videos, playlist extraction and a free get_credits balance check (13 tools).
This is a first-party entry: the server is published by the vendor of the service it calls (I work on GetYouTubeTranscript), so it falls under the "official vendor" case in the registry criteria; the backend is the vendor's hosted API. Auth is a bearer API key, which would be declared as a secret. The service is metered (new accounts get 100 free credits). It is also listed in the official MCP Registry as com.getyoutubetranscript/youtube-transcript-and-youtube-search.
Basic Requirements
- Open Source: Uses acceptable license (Apache-2.0, MIT, BSD-2-Clause, BSD-3-Clause or other permissive license) — MIT
- MCP Compliant: Implements MCP API specification —
initializereturns protocol2025-06-18,tools/listreturns 13 tools (checked 2026-11-20) - Active Development: Recent commits and maintained — last push 2026-11-19
- Documentation: Basic README and setup instructions — README plus https://getyoutubetranscript.com/youtube-mcp-server
- Security Contact: Method for reporting security issues — SECURITY.md in the repository
Submitter Checklist
- I have read the MCP Server Registry Inclusion Heuristics
- This server meets the basic requirements listed above
- I understand this will undergo automated and manual review based on Registry Management
If approved, I will open the PR with a remote server entry referencing this issue.
- Dominant language
- Go
- Stars
- 26
- Forks
- 104
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 88
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from stacklok/toolhive-catalog
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
stacklok/toolhive-catalog#1986 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
stacklok/toolhive-catalog#1976 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
stacklok/toolhive-catalog#1969 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
stacklok/toolhive-catalog#1968 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
stacklok/toolhive-catalog#1967 ·
Maintainers usually reply within 1 day
All issues in stacklok/toolhive-catalog
Similar issues
-
HTTP probe loses insecureSkipVerify in the generated probe manifestPossibly taken @BahaaMattar claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
litmuschaos/litmus#5745 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 2 days
-
type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
messaging/v1: IsGRPCProtocol and InternalMetadataToGrpcMetadata panic on empty or nil metadata valuesPossibly taken @patelshivani2283-lab claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day