YouTube MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is YouTube MCP Server?

YouTube MCP Server is a Model Context Protocol (MCP) server designed for interacting with YouTube data, allowing users to query videos, channels, comments, and transcripts through a standard input/output interface.

how to use YouTube MCP Server?

To use the server, you can install it via Smithery or manually clone the repository, install dependencies, and set up your environment variables. After that, you can build and run the server to start querying YouTube data.

key features of YouTube MCP Server?

  • Advanced video search with filtering options
  • Detailed information retrieval for videos and channels
  • Comparison of statistics across multiple videos
  • Discovery of trending videos by region and category
  • Analysis of channel performance and video statistics
  • Retrieval of video comments and transcripts
  • Generation of video analysis and transcript summaries

use cases of YouTube MCP Server?

  1. Analyzing video performance metrics for content creators.
  2. Retrieving transcripts for educational videos.
  3. Comparing statistics of competing videos for market research.
  4. Discovering trending content in specific regions.

FAQ from YouTube MCP Server?

  • What are the prerequisites for using the server?

You need Node.js (v16+) and a YouTube Data API key.

  • How can I deploy the server using Docker?

You can build the Docker image and run the container with the provided commands in the documentation.

  • What types of data can I query?

You can query video details, channel statistics, comments, and transcripts.

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

Recommend Servers

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

2 days ago