YouTube Shorts Agent MCP Server

What the code does

We read the source, 1 d ago · rules 995398eba69f

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    return path.join(this.baseDir, name);

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add youtube-shorts-agent -- npx -y youtube-shorts-agent

{
  "mcpServers": {
    "youtube-shorts-agent": {
      "command": "npx",
      "args": [
        "-y",
        "youtube-shorts-agent"
      ]
    }
  }
}

[mcp_servers.youtube-shorts-agent]
command = "npx"
args = ["-y", "youtube-shorts-agent"]

{
  "mcpServers": {
    "youtube-shorts-agent": {
      "command": "npx",
      "args": [
        "-y",
        "youtube-shorts-agent"
      ]
    }
  }
}

{
  "servers": {
    "youtube-shorts-agent": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "youtube-shorts-agent"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: YOUTUBE_DRY_RUN (Set to false only when the agent should perform live YouTube upload operations. Defaults to dry-run behavior), YOUTUBE_CLIENT_ID (Google OAuth client ID. Optional until OAuth or live upload flows are used), YOUTUBE_CLIENT_SECRET (Google OAuth client secret. Keep local and do not expose it to agents).