Build SEO tools from Claude, plus FRED and five AI stories

Today we're going to use qbash to build our own set of SEO tools that we can call from Claude, Chatg GPT, or really any agent that supports MCP. By the end, you'll be able to ask Claude what to fix on your site, and your own tools will give you the answer. First, we'll add the Cube Bash MCP to Claude. Quick note, if you're on a team or enterprise plan, your account owner has to add custom connectors. So, you might need to ask them to set this up for you.

Otherwise, open customize, then connectors, click add, and choose add a custom connector. Give it a name like qbash MCP. Paste in the address you see on the screen and click continue. Then click connect and sign in with your qbash account. A free Cube Bash account works fine.

Now, in a new chat, open the plus menu, go to connectors, and turn qbash on. Next, we're going to give qbash some context about your business. In qbash, open memories and make a new folder called SEO Knowledge. In there, add a document called keyword priorities with the topics you care about, the searches people use for each one, and the pages you want to rank for. Then add a document called brand voice.

That's where your tone goes along with how you like your page titles and articles written. Now for the fun part. We're going to have Claude build us a QBash task that pulls your data and your context together into tools that you can call. Just tell Claude the kinds of questions you ask, the accounts you want to pull data from, like search console or ah refs, and point it at your SEO knowledge folder. Claude hands that off to the qbash task builder, which writes the task and saves each version in qbash.

What you end up with is one task called SEO tools with a mode for each of your questions. The task needs access to your accounts. So, qbash will ask you to connect them. Click connect and sign in with Google for search console and analytics. You can also add Google ads for monthly search volume and ah refs for keyword difficulty if you want it.

Ah refs needs your own API key. Okay, let's try it in Claude. Ask a question and mention SEO tools so Claude knows to use it. Something like what should I fix this week? SEO Tools runs in qbash and comes back with five pages, how many searches they get a month, and suggested fixes.

Every run has a detailed login cube bash, so you or your agent can check exactly where each number came from. You could tell Claude to run this every Monday morning, and that schedule shows up under triggers in qbash. Every run gets saved there with its log. The same tools work in chat GPT, Grockbot, or anything else that takes an MCP. In Chat GPT, qbash shows up under plugins with the same address.

Ask it what pages you should write next, and SEO tools will tell you what's worth adding. You can start free at cubash.com. Build your own SEO tools and then build tools for the other questions you ask every week.

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.

qbash connects Claude to Fred, the Federal Reserve's economic database. I asked Claude to connect Fred through qbash. It gives me a link to add to my Fred API key. I paste in my key and save it. Now, I can ask about the economy in plain English.

Claude finds the right series and pulls the numbers. Here's inflation since 2020 next to the Fed funds rate charted from the real data. It can also check the release calendar, so I know when new numbers land. Connect Fred to qbash to get it started.

So this is the official qbash MCP server. You can add it to claude, chat, GPT, codeex, cursor, whatever you use uh with one URL. And from your chat, you can build Python tasks. You can run them, look at their logs, schedule them to run. You can use apps you've connected and share memory across your agents.

All kinds of stuff. I'm going to show you what that looks like in Claude. going from a quick question to a task that runs every morning. So, first I copy the server address from here in claude. I go to connectors.

I add a custom connector called qbash and paste it in. Now, I already have a Cube Bash account, so I just sign in. If you don't, you can sign up right here, and you'll land back in Claude afterwards. I approve Claude's access and qbash is connected. In a new chat, I ask what qbash can do.

It works with the apps I connect, builds tasks that run on their own, and keeps memory. So, here's my scenario today. We're a small coffee roaster, and our inventory lives in this Google sheet. Uh, what's on hand, what sold last week, and who supplies each item? Right now, someone checks it by hand every morning to work out what to reorder.

I'd like that done for me. So, I ask Claude to connect my Google Drive. It gives me a link and I sign into Google. Back in Claude, I ask what's running low. It reads the sheet and shows how many weeks each item has left and who supplies it.

I want something I can act on. So, I ask how much to reorder for 4 weeks of stock grouped by supplier. That's what I want to run every morning. So, I ask Claude to turn it into a task. The card shows qbash writing it and testing it.

Then I run it and the run card follows along. Now, same list, but now it comes from a task. Let me open it in qbash. You don't have to look at this, but it's here if you want to review it. This is real Python that qbash wrote and the log from the run I just did.

There's a full editor in here too, but you can do all this from Claude over MCP. And that's how we like to do it, too. Back in Claude, I ask for one more change. Post the list to our demo channel in Slack. The Slack isn't connected yet, so I sign into Slack from the link.

qbash updates the task and runs it again. And here it is in Slack. Finally, I ask Claude to run it every weekday at 9:00 a.m. Now it runs on its own every morning, even when Claude is closed, even when my laptop is off. So, from one chat, I connected Drive and Slack, worked out the reorder list, and turned it into a scheduled task that I can change just by asking.

The official MCP servers address and the setup for each app are here on qbash.com under docs, official MCP server. Check it out.

Hey, Jack from qbash here. Um, today I'm going to be running you through how we hook up qbash's global MCP server to Muse. Um, so this is assuming you have a Muse account already set up or a Meta account and you have a qbash account set up. So I have a fresh chat here in Muse. Um, what I'm going to do first is come to Qbash.

We're in the build page. We're going to head to MCP servers. We're going to pick the official MCP server. Um, you can see here we have MU specific instructions. So, we're going to copy this MCP link.

We're going to come back to our chat and we're going to say, um, can you add this MCP server uh to your system for use? Okay, so Muse has processed the request. Um, we need to give it permission to communicate with the MCP server. I'm just going to pick always allow for this instance. Uh but feel free to allow once and test first before you give it global permissions there.

Um we'll let this process and we'll come back once it's ready for the next step. Okay, so with Muse being able to write client code on the fly. It's been able to hook up our MCP server here and all we need to do is go through the OOTH. So we're going to connect qbash to Muse here and we're going to allow a sign in and we're going to pick the Isisle of Code account. Okay, now that the MCP server is hooked up, um, let's do a test.

So, in qbash, I've created, uh, an MCP demo memory folder, and I have a file in here called MCP smoke test, which just has content saying that it's proof that the MCP has been connected. So, let's grab this folder name here, and let's say uh, let's ask Muse, tell me what's inside the memory folder. qbashmuse mcp demo. And that'll just confirm that the MCP server has been hooked up. Great.

Muse has got back to us. Um, it's found the content. That content matches the memory and we should be good to go. That's how you get cube bash hooked up to Muse.