48 Hours Building a YouTube MCP Connector for Grok with Cline

It started with one line typed into Cline:

“I’d like to look into setting up an MCP to allow outside agents to upload videos to a YouTube account. Use websearch to look into this.”

Roughly 48 hours later, Grok could upload videos through it.

This is the unfiltered story of what that actually took.

The Gap Between the Dream and Reality

The fantasy version is simple: you give an AI a goal and it builds the tool.

The real version involved constant correction. Cline kept drifting toward building the MCP in a way that was convenient for itself rather than exposing clean, callable tools for outside agents. Every time it went off on one of these loops, it had to be pulled back.

There was also a steep, on-the-fly education in Google Cloud OAuth, consent screens, and why uploads were randomly failing. It was not elegant.

The Google Drive Bridge

One of the simplest yet most effective breakthroughs was the Google Drive integration. Setting a folder or files to “Anyone with the link” made uploads reliable without a lot of extra hassle.

The working flow became:

• Finish the Short and place it in the shared Google Drive location
• Grab the public share link
• The connector handles the rest — uploading to YouTube with titles, descriptions, privacy settings, and all the metadata applied automatically

It started as a practical hack and turned into something that just works. Sometimes the simplest bridge is the one that doesn’t need to be pretty.

The Motivation That Actually Mattered

There was a $100 bet involved, which helped. But the stronger driver was simpler: the satisfaction of making powerful connections work. Being able to say “make a short and upload it” and have it actually be possible creates a different kind of leverage.

Most current workflows still involve local models + manual steps. This one removes several of those steps.

What Actually Feels Different

Exposing the YouTube API through the connector so that Grok can use it directly isn’t revolutionary on its own. What feels new is the combination of strong prompt work, a custom assembly step, and direct publishing that removes a lot of the usual friction.

The Flow: Idea to Published Short

It starts with pitching an idea. Grok researches the topic and generates a complete script, broken into short segments with ready visual prompts.

Any number of 10-second clips can then be created and brought back. A custom concatenation script stitches them together into a finished Short, handling music, captions, transitions, and pacing so it feels like one continuous piece.

From there the connector takes care of the entire upload process — applying an optimized title, description, tags, thumbnail, and playlist placement automatically.

After it’s live, the same setup makes it simple to check in on comments, threads, and engagement without extra tools or context switching.

The loop from idea to researched script to assembled Short to published video to ongoing conversation turns what used to be scattered tasks into something that flows naturally from start to finish. That’s the part that actually feels different.

Current State

The connector can create playlists, upload videos, manage comments, and handle basic metadata. Auth is still annoying. Some edge cases are janky. But the important part works — and the full pipeline from script generation through concatenation to publishing is now genuinely usable.

It went from a vague research request to something usable in about two days of very directed effort. That part, at least, feels honest.