Youtube Translate

Created By
brianshin22a year ago
An MCP server for interfacing with the Youtube Translate API. Create transcripts, translations, subtitles, summaries for any Youtube video (or any other platform). Search video transcripts for keywords and phrases. Directly processes videos to understand them.
Overview

What is YouTube Translate?

YouTube Translate is a Model Context Protocol (MCP) server that interfaces with the YouTube Translate API, enabling users to create transcripts, translations, subtitles, and summaries for any YouTube video.

How to use YouTube Translate?

To use YouTube Translate, install the package via Smithery or manually, set your YouTube Translate API key, and run the server using the provided commands.

Key features of YouTube Translate?

  • Obtain transcripts of YouTube videos
  • Translate transcripts into various languages
  • Generate subtitles in SRT or VTT format
  • Create summaries of video content
  • Search for specific keywords within video transcripts

Use cases of YouTube Translate?

  1. Generating subtitles for educational videos.
  2. Translating video content for a global audience.
  3. Summarizing lengthy video content for quick understanding.

FAQ from YouTube Translate?

  • Is YouTube Translate free to use?

Yes! YouTube Translate is free to use, but you need a valid YouTube Translate API key.

  • What programming language is required?

YouTube Translate requires Python 3.12 or higher.

  • Can I run YouTube Translate using Docker?

Yes! You can run the server using Docker for easier deployment.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
brianshin22
Star
-
Language
-
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.

21 hours ago