Fawad Naseem Let’s talk

AI media infrastructure / published

YouTube MCP Server

A published MCP server that gives an AI client five focused YouTube operations: get a video, search, upload, update metadata, and delete. Each tool routes to its own n8n workflow for maintainable, auditable execution.

System flow

  1. Receive an MCP call from the AI client
  2. Select one of five purpose-built YouTube tools
  3. Route execution to the matching sub-workflow
  4. Call the YouTube operation and return its result to the client

What this proves

  • Published MCP Server Trigger is visible in n8n
  • Five named tools cover the main YouTube content lifecycle
  • Modular routing keeps each API operation isolated and maintainable

More case studies

Need something like this?

Let’s make it actually work.