YouTube Caption MCP Server

Created By
iamyosukea year ago
An MCP server for cursor to retrieve YouTube video captions without requiring an API key.
Overview

What is YouTube Caption MCP Server?

YouTube Caption MCP Server is a tool that allows users to retrieve YouTube video captions without needing an API key, utilizing the youtube-js library to access YouTube's internal API.

How to use YouTube Caption MCP Server?

To use the server, install it via NPM or build it from source, then configure it in your Cursor settings to enable caption retrieval for YouTube videos.

Key features of YouTube Caption MCP Server?

  • No API Key Required: Access YouTube's internal API without an API key.
  • Multilingual Support: Automatically detects and retrieves available caption languages.
  • Format Conversion: Outputs captions in Raw, SRT, and VTT formats.
  • Caching: In-memory caching for improved performance.
  • Claude Integration: Seamless integration via MCP protocol.

Use cases of YouTube Caption MCP Server?

  1. Retrieving captions for educational videos.
  2. Downloading subtitles for video content in various formats.
  3. Searching for videos with specific caption languages.

FAQ from YouTube Caption MCP Server?

  • Can I use this tool without an API key?

Yes! This tool is designed to work without requiring an API key.

  • What formats can I download captions in?

You can download captions in Raw, SRT, and VTT formats.

  • Is there support for multiple languages?

Yes! The server automatically detects and retrieves available caption languages.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
iamyosuke
Star
1
Language
TypeScript
License
MIT license

Recommend Servers

View All
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.

8 hours ago