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
Voyei

2 hours ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago