YouTube Transcript Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is YouTube Transcript Server?

YouTube Transcript Server is a Model Context Protocol server that enables users to retrieve transcripts from YouTube videos, providing direct access to video captions and subtitles through a simple interface.

how to use YouTube Transcript Server?

To use the server, install it via Smithery or the command line, and then call the get_transcript tool with the YouTube video URL or ID to extract the transcript.

key features of YouTube Transcript Server?

  • Support for multiple video URL formats
  • Language-specific transcript retrieval
  • Detailed metadata in responses

use cases of YouTube Transcript Server?

  1. Extracting subtitles for video content analysis
  2. Generating transcripts for accessibility purposes
  3. Retrieving captions for language learning applications

FAQ from YouTube Transcript Server?

  • Can I retrieve transcripts in different languages?

Yes! You can specify the language code for the transcript retrieval.

  • What happens if the video has no available transcript?

The server will handle this gracefully and provide an appropriate error message.

  • Is there a limit to the number of transcripts I can retrieve?

There are no specific limits, but be mindful of YouTube's API usage policies.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
License
-

Recommend Servers

View All
Voyei

3 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

13 hours ago