Agent-first YouTube Shorts uploader: dry-run validation, OAuth checks, synthetic-media metadata.
Agent-first YouTube Shorts uploader: dry-run validation, OAuth checks, synthetic-media metadata. The youtube shorts agent mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 6 defined tools rather than through you.
Everything the assistant can do here goes through one of these:
youtube_agent_manifest — Install/runtime guidance for Codex, Claude, Cursor, Hermes and OpenClawyoutube_connection_status — OAuth and dry-run readiness without token valuesyoutube_privacy_audit — Upload scope, synthetic media and local file boundariesyoutube_oauth_authorize_url — PKCE authorization URL with local session storageyoutube_upload_short — Dry-run or live Shorts uploadyoutube_list_recent_videos — Lightweight channel verificationYou will need 4 environment variables: YOUTUBE_CLIENT_ID, YOUTUBE_CLIENT_SECRET, YOUTUBE_ACCESS_TOKEN, YOUTUBE_REFRESH_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Installation goes through your MCP client rather than a global install: point it at args on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Plenty of file and storage access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. YouTube Shorts Agent's toolset — youtube_agent_manifest, youtube_connection_status, youtube_privacy_audit and 3 more — is a fair guide to whether it matches your workflow. It is maintained by davidmosiah; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| youtube_agent_manifest | Install/runtime guidance for Codex, Claude, Cursor, Hermes and OpenClaw |
| youtube_connection_status | OAuth and dry-run readiness without token values |
| youtube_privacy_audit | Upload scope, synthetic media and local file boundaries |
| youtube_oauth_authorize_url | PKCE authorization URL with local session storage |
| youtube_upload_short | Dry-run or live Shorts upload |
| youtube_list_recent_videos | Lightweight channel verification |
{
"mcpServers": {
"youtube-shorts-agent": {
"command": "npx",
"args": ["-y", "args"],
"env": {
"YOUTUBE_CLIENT_ID": "your-value",
"YOUTUBE_CLIENT_SECRET": "your-value",
"YOUTUBE_ACCESS_TOKEN": "your-value",
"YOUTUBE_REFRESH_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| YOUTUBE_CLIENT_ID | Configuration value read at startup. | Optional |
| YOUTUBE_CLIENT_SECRET | Credential the server authenticates with. | Yes |
| YOUTUBE_ACCESS_TOKEN | Credential the server authenticates with. | Yes |
| YOUTUBE_REFRESH_TOKEN | Credential the server authenticates with. | Yes |
Scoped local file access — read, write, search and reorganise files in directories you explicitly allow.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Chat with your second brain — search, read and write vault notes through the Local REST API.
Connects AI models to an Obsidian knowledge base for direct access and manipulation of notes and folders.