My YouTube MCP Server

Created By
airballoonappa year ago
mcp-youtube-uploader server (youtube to s3)
Overview

What is My YouTube MCP Server?

My YouTube MCP Server is a server that facilitates the searching, downloading, and uploading of YouTube videos to Amazon S3, with optional integration into TwelveLabs.

How to use My YouTube MCP Server?

To use the server, follow these steps:

  1. Install the necessary dependencies using npm install.
  2. Build the project with npm run build.
  3. Run the server locally using npm start.

Key features of My YouTube MCP Server?

  • YouTube video searching capability.
  • Downloading videos from YouTube.
  • Uploading videos directly to Amazon S3.
  • Optional import of videos into TwelveLabs.

Use cases of My YouTube MCP Server?

  1. Content creators can download their YouTube videos and store them on S3 for backup.
  2. Developers can integrate YouTube video functionalities into their applications.
  3. Users can manage their video content efficiently with cloud storage.

FAQ from My YouTube MCP Server?

  • Can I upload any YouTube video?

Yes, as long as you have the rights to the video, you can upload it to S3.

  • Is there a limit to the number of videos I can upload?

The limit depends on your S3 storage plan.

  • Do I need to set up an AWS account?

Yes, you will need an AWS account to use the S3 upload feature.

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

Recommend Servers

View All
Payai X402 Tools

8 hours 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