Skip to main content

Claude Code builds a qbash Task that posts videos to YouTube, LinkedIn and X

Mitchell Tessier

In this video Mitch walks through the official qbash MCP server, then has Claude Code post a video to YouTube, LinkedIn and X with a qbash Task. The Task takes a video, writes copy for each platform, posts it and saves it to an archive. Along the way Claude Code finds that the MCP has no tool for sending a local file to a Task, so it builds a small helper Task that uploads the file first.

What's covered

  • What the official qbash MCP server lets an agent do
  • The video posting Task and its run inputs
  • Asking Claude Code to post a video from the local machine
  • The helper Task Claude Code built to upload the file
  • The run logs and the finished posts on YouTube, LinkedIn and X

What the official qbash MCP server does

qbash has supported custom MCP servers for a while. You bind Tasks, memories and specific functions to a custom server and share it with teammates or customers. The official qbash MCP server gives an agent the whole account instead. In Mitch's words:

"This gives agents the ability to find and execute tasks as tools, build their own tasks, manage memories... access any connectors... basically do everything that you can do on qbash, you can do it from an agent."

Each runnable Task becomes one MCP tool, and its schema comes from the Task's current inputs. Mitch uses the server with coding agents and with Grok Bot, which he runs every day.

The video posting Task

Posting and managing demo videos is admin work that takes Mitch out of the flow, so he had Claude build a Task for it. The Task takes a Google Drive link, a transcript, a brief and a few parameters. It writes copy for each platform, posts the video from the company accounts connected in qbash and saves the result to an archive. It covers the job a tool like Hootsuite once did, bound to the accounts the team already runs.

Post a video from Claude Code

In a fresh Claude Code session, Mitch asks Claude to use the Task through the qbash MCP to upload a video file from his machine, and pastes in its transcript. The video is Alex MacLeod's FRED walkthrough.

When the run finishes, Claude reports that the video is live on all three platforms and links each post. The qbash MCP had no tool for sending a local file to a Task, so Claude built a small helper Task to do it. Claude re-encoded the video, ran the posting Task as a dry run, and then ran it for real.

A helper Task with no AI in it

The helper Task has no AI step. It calls the Task SDK's file upload function, which returns a temporary URL, and the posting Task reads the video from that URL. The helper is saved in qbash like any other Task, so Claude Code can call it the next time it needs to send a local file to a Task.

The run logs and the posts

The run log in qbash lists every step the posting Task went through. On YouTube the video has a title and description written for YouTube. The LinkedIn post on the company page opens with a hook, carries hashtags and ends by pointing to the qbash MCP. On X it's a short post with the video attached. The Task wrote each one from the transcript.

Official MCP server has the server URL and the setup steps for Claude Code, Codex, Cursor, ChatGPT and other MCP clients.

Open qbash →

Video transcript

Hey guys, Mitch from qbash here. Bunch of updates in this video. So, first, as some of you have probably already seen or heard, we released our official qbash MCP server last week. We've supported MCP servers for a while. We've been on a real journey with MCP servers.

Actually, our custom MCP execution servers. These are the things where you can bind tasks and memories and specific functions to a custom MCP and then distribute that to different people across your team or your customers or whoever it might be. The official MCP server, the qbash MCP is a different beast and it's super powerful. This gives agents the ability to find and execute tasks as tools, build their own tasks, manage memories, build new memories, folders, and store things. Memories, access any connectors, third party tools that you might have on the platform.

Basically do everything that you can do on qbash, you can do it from an agent. This has really changed the way that we've worked. using it with our coding agents, using it with always on agents like I use Grockbot as a daily driver. And this has been really powerful in combination with that essentially these agents building the tools that they need, accessing the memories that they need, being able to share information across different setups. So having Grockbot researching things, putting together a brief that it's handing off to Claude Code to build a new feature or something like that.

So, completely changed the way that we work. And as a bit of an example of that, I wanted to show you a task that I had Claude build for me. Just to alleviate some of the admin stuff that I do, we love making these videos. I love making these demo videos. Posting them and managing them, it can be a bit of a headache.

It's an admin load. It takes me out of the flow. I [sighs] had Claude build this task that takes a Google Drive link, a transcript, a brief, and there's some parameters here, takes all of that, and essentially it's a pipeline. It's like this micro application once upon a time. It's the kind of thing you might have looked at at like Hootuite to be able to do.

Um, but it's this micro application that's bound to the company accounts that we run or personal accounts. for me takes a video and writes all the copy, posts it in multiple different places, saves it in an archive just as like this pipeline, this one thing. And with the MCP, you can connect that to something like Claude Code where you might be producing videos anyway, right? Some of the demo videos, the demo portions that we do, some of the more buttoned up ones, that's the some of that is generated. I think it's a really cool idea.

Let's take a look at trying this out. So, I'm going to copy the name of this, right? And I'm going to open up a fresh terminal window. Let me zoom in for everyone. Okay.

And let's just bump open Claude. Cool. And let's say use dev video tox LinkedIn YouTube on cubashmcp to upload the following video and I will drop in that file. Here is a transcript. We can ignore that.

Yeah, here is a transcript. Cool. This is a cool video that Alex Mloud put together that looks at a new connector that we have coming up, which is a Fred connector allowing you to query the Fred economic database. I'm going to let this run and come back with the result and we can see how it works. Okay, and we're back.

Let's see how it went. So, yes, it is live on all three platforms. Here are the links. Interesting. Cubes has no tool for sending a local file to a task.

So, I built a small helper task. Dev upload file helper. Thank you for solving that. It re-encoded the video file first. It did a dry run, took that copy, and then did the real run.

So, if we go to qbash here, what we'll see is a great example of what I was saying before. [snorts] Claude code encountered a problem, right? and it built its own task to solve that problem. And now if I was to do this again in the future, it could call this task and use that. And this task, I think, again, this is the cool stuff that we're finding all the time.

There's no AI in this task, right? It's just uploading a file, looking at that file. qbash task SDK has a file upload function, right, where it'll return the URL. And so it's built a task that does that and gives you the temporary URL and then it's using that URL to send to the secondary task and upload. That to me is really cool.

If I look back in here at the logs, you can see this one passed. These are all the steps that it went through and it uploaded those, right? And now if we go and look at company X account LinkedIn and YouTube. We have the video uploaded in all three places. Federal Reserve data include connect Fred through the official qbash MTP with metadata in here formatted for YouTube.

LinkedIn post uploaded here has some hashtags. I don't know if hashtags are still a thing but very much formatted like a LinkedIn post right it has a hook it has this talking about the MCP as a CTA and on X it's a short tweet with the video Federal Reserve data include via the qbash MCP add your Fred API key then ask in plain English etc. So it's taken all of that information from the transcript and it's written copy and metadata for each platform. I hope this video kind of shows you some of the power of the MCP and the kind of things you can build and the problems that these agents can now solve for you. We're really excited about it.

Thanks, guys. Talk to you soon.

Stay in the loop

Product updates, tutorials, and AI insights. No spam.