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 implementation that utilizes the YouTube Data API, allowing AI language models to interact with YouTube content through a standardized interface.

how to use YouTube MCP Server?

To use the YouTube MCP Server, you can install it via npm or Smithery, configure your environment with the required YouTube API key, and then utilize various MCP tools to interact with YouTube data.

key features of YouTube MCP Server?

  • Retrieve detailed video information including title, description, and statistics.
  • Manage video transcripts with multi-language support.
  • Analyze channel statistics and growth metrics.
  • Access trending videos by region and category.

use cases of YouTube MCP Server?

  1. Analyzing video engagement metrics for content creators.
  2. Retrieving and displaying video transcripts for accessibility.
  3. Monitoring trending content in specific categories for market research.

FAQ from YouTube MCP Server?

  • What is required to run the YouTube MCP Server?

You need Node.js 18.0.0 or higher and a valid YouTube Data API key.

  • Can I customize the language for video transcripts?

Yes, you can specify language preferences for transcripts in the configuration.

  • Is there a license for this project?

Yes, the project is licensed under the MIT License.

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
Tavily Mcp
@tavily-ai

JavaScript
a year 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.

5 hours ago