Maagpi Youtube Workflow Skill MCP Server

Claude Code skill: end-to-end YouTube production pipeline run by a persistent per-channel agent team (researcher + uploader long-lived, topic-runner

Local serverstdio

What is the Maagpi Youtube Workflow Skill MCP server?

Claude Code skill: end-to-end YouTube production pipeline run by a persistent per-channel agent team (researcher + uploader long-lived, topic-runner ad-hoc, cap 3 concurrent), with intra-topic fan-out, per-step checkpoint resume, and. Exposed over MCP by the maagpi youtube workflow skill mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

YouTube Content Workflow is a Claude Code skill that turns a Notion content calendar into scheduled YouTube videos end-to-end: pick a channel, generate SUCCESS-framework titles, run NotebookLM deep research, generate an Explainer video in the channel's language, transcribe it, draft the description, build the thumbnail (preferring Nano Banana Pro), generate tags, and schedule upload — never public.

  • Anti-hallucination by construction. — Tool-sourced facts only, per-step output verification, language preservation. Never invents topics, calendar entries, or transcripts
  • Parallel by default. — Title gen and the heavy per-topic pipeline both fan out as subagent teams; user gates (title pick, review, privacy) batch sequentially
  • Never public. — Default privacy is private. unlisted requires explicit opt-in. A pre-flight assertion enforces this before every upload call

Its toolset

Everything the assistant can do here goes through one of these:

  • Trigger — ** /youtube-content-workflow
  • State — ** local JSON cache (per-channel + per-run) + Notion (canonical)
  • Transcription — dedicated MCP, NotebookLM studio_status transcript field, or local whisper (auto-detected, in that order)
  • youtube-content — workflow** (~/.claude/skills/youtube-content-workflow/SKILL.md) - End-to-end YouTube production pipeline. Trigger: /youtube-content-workflow
  • Anti — hallucination by construction.** Tool-sourced facts only, per-step output verification, language preservation. Never invents topics, calendar
  • Reference — SUCCESS framework — Heath brothers, Made to Stick
  • Phase — What it does
  • Manual — Then append the registration block to ~/.claude/CLAUDE.md so the slash command dispatches:

Adding it to your client

youtube-content-workflow on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration

The skill orchestrates external MCPs at runtime. Install these in your Claude environment before first use — Phase 0 of the skill probes each one and halts with the exact missing-tool name if any are absent. - Notion MCP — read the content calendar, write per-channel context - NotebookLM MCPnotebook_create, research_start (deep mode), studio_create, download_artifact ·

When to reach for it

This sits in the planning and project tracking group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Maagpi Youtube Workflow Skill's toolset — Trigger, State, Transcription and 5 more — is a fair guide to whether it matches your workflow. It is maintained by vamsi-kodimela; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the maagpi youtube workflow skill mcp server does with a few real requests.

Available tools

ToolWhat it does
Trigger** /youtube-content-workflow
State** local JSON cache (per-channel + per-run) + Notion (canonical)
Transcriptiondedicated MCP, NotebookLM studio_status transcript field, or local whisper (auto-detected, in that order)
youtube-contentworkflow** (~/.claude/skills/youtube-content-workflow/SKILL.md) - End-to-end YouTube production pipeline. Trigger: /youtube-content-workflow
Antihallucination by construction.** Tool-sourced facts only, per-step output verification, language preservation. Never invents topics, calendar entries, or transcripts.
ReferenceSUCCESS framework — Heath brothers, *Made to Stick*
PhaseWhat it does
ManualThen append the registration block to ~/.claude/CLAUDE.md so the slash command dispatches:

How to install the Maagpi Youtube Workflow Skill MCP server

{
  "mcpServers": {
    "maagpi-youtube-workflow-skill": {
      "command": "npx",
      "args": ["-y", "youtube-content-workflow"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

The skill orchestrates external MCPs at runtime. Install these in your Claude environment before first use — Phase 0 of the skill probes each one and halts with the exact missing-tool name if any are absent. - Notion MCP — read the content calendar, write per-channel context - NotebookLM MCPnotebook_create, research_start (deep mode), studio_create, download_artifact ·

Example prompts to try

  • Use Maagpi Youtube Workflow Skill to Trigger.
  • Use Maagpi Youtube Workflow Skill to State.
  • Use Maagpi Youtube Workflow Skill to Transcription.

Frequently asked questions

It connects Maagpi Youtube Workflow Skill to MCP-compatible AI assistants such as Claude and Cursor, exposing 8 tools (Trigger, State, Transcription, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Maagpi Youtube Workflow Skill directly.