YouTube MCP Server

Created By
Tisik79a year ago
A Media Control Protocol server for YouTube integration
Overview

What is YouTube MCP Server?

YouTube MCP Server is a Media Control Protocol server designed for integrating YouTube playback control across multiple devices.

How to use YouTube MCP Server?

To use the YouTube MCP Server, clone the repository, install the dependencies, set up your YouTube API key in the .env file, and start the server. Access the interface via your browser at http://localhost:3000.

Key features of YouTube MCP Server?

  • Control YouTube playback (play, pause, seek) from any device.
  • Synchronize playback across multiple clients.
  • Search for YouTube videos directly from the interface.
  • Real-time updates using WebSockets.
  • Simple and intuitive user interface.

Use cases of YouTube MCP Server?

  1. Controlling YouTube playback in a group setting.
  2. Synchronizing video playback for presentations or events.
  3. Developing custom applications that require YouTube video control.

FAQ from YouTube MCP Server?

  • Can I control playback from multiple devices?

Yes! The server allows you to control playback from any connected device.

  • Do I need a YouTube API key?

Yes, you need to set up a YouTube API key to use the server.

  • Is the server easy to set up?

Yes, the setup process is straightforward with clear instructions provided in the documentation.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Tisik79
Star
0
Language
JavaScript
License
MIT 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.

a day ago