YouTube Shorts Agent
Validate and upload YouTube Shorts from an agent with dry-run defaults, OAuth checks, and synthetic-media metadata handling.
Overview
YouTube Shorts Agent is an MCP server for the Launch phase that lets AI agents dry-run, authenticate, and upload YouTube Shorts with synthetic-media metadata controls.
What is this MCP server?
- Agent-first MCP (youtube-shorts-agent npm 0.1.6) with stdio transport for coding agents
- Dry-run by default via YOUTUBE_DRY_RUN until you explicitly opt into live uploads
- Google OAuth client ID and secret for upload and auth verification flows
- Synthetic-media metadata support aligned with agent-generated or AI-assisted Shorts workflows
- Repository: github.com/davidmosiah/youtube-shorts-agent
- Server version 0.1.6
- Three documented environment variables: YOUTUBE_DRY_RUN, YOUTUBE_CLIENT_ID, YOUTUBE_CLIENT_SECRET
- Stdio npm identifier: youtube-shorts-agent
What problem does it solve?
Publishing Shorts from an agent pipeline is risky without a default dry-run gate and a dedicated YouTube OAuth upload path.
Who is it for?
Solo creators and indie SaaS marketers who already use MCP and want scripted Shorts distribution with safe defaults.
Skip if: Teams needing full YouTube analytics, community management, or non-Shorts long-form scheduling in one server.
What do I get? / Deliverables
Your agent can validate upload payloads and OAuth, then perform live Shorts uploads only when you disable dry-run explicitly.
- Dry-run validation of Shorts upload operations before live publish
- OAuth-verified upload path when YOUTUBE_DRY_RUN is false
- Metadata handling suitable for agent-generated or synthetic Shorts
Recommended MCP Servers
Journey fit
Short-form video publishing is a Launch-phase distribution move after the product or clip exists and you need repeatable outbound channels. Distribution fits because the MCP focuses on getting Shorts onto YouTube with guardrails, not on editing timelines or ad buying.
How it compares
MCP upload adapter for YouTube Shorts, not a video editor skill or a multi-platform social scheduler.
Common Questions / FAQ
Who is YouTube Shorts Agent for?
Builders and creators using Claude Code or Cursor who want agents to handle Shorts upload validation and publishing via MCP.
When should I use YouTube Shorts Agent?
Use it at Launch when you are distributing Shorts and want dry-run checks before flipping live uploads with Google OAuth.
How do I add YouTube Shorts Agent to my agent?
Add the npm package youtube-shorts-agent as a stdio MCP server, set YOUTUBE_CLIENT_ID and YOUTUBE_CLIENT_SECRET locally, keep YOUTUBE_DRY_RUN enabled until you are ready to upload.