This video connects Muse to the official qbash MCP server in about two minutes. After an OAuth sign-in, Muse can build and run Tasks, read and write memory folders, and call the connectors in your qbash account. The same URL works in Claude, ChatGPT, Grok Bot, Claude Code, Codex and Cursor.
What's covered
- Copying the server URL from the Muse instructions on the official MCP server page
- Asking Muse to add the server, and choosing how long to allow it
- Signing in with qbash and picking an organization
- A smoke test that reads one document from a memory folder
Copy the server URL
You need a Muse account and a qbash account. In qbash, open Build, then MCP Servers, then Official qbash MCP server. The page shows the URL, https://mcp.qbash.com/mcp, and a row of client tabs under Connect with OAuth. The Muse tab has three steps: open a Muse chat, ask it to add the server, and complete the qbash authorization flow. Copy the URL from step two.
Ask Muse to add it
Open a fresh Muse chat and paste: "Can you add this MCP Server to your system for use: https://mcp.qbash.com/mcp". Muse asks for permission to talk to the server. Jack picks Always allow in the video. You can allow once, test, and only then give it standing permission.
Muse writes its own client code for the server, so there is nothing to install. It replies with what it found and what it is requesting: read and call access to the server's tools, plus openid and offline_access so the sign-in stays connected. It also points out that qbash issues this access through its own sign-in, so no application or API key is needed first. A Qbash connector card appears with a Connect button.
Sign in with qbash
Connect opens the qbash authorization page. It shows the account that is signing in, the organizations that account belongs to, and what Muse will be able to do. Muse can see tasks, run history, memories and connectors. It can run tasks, build new tasks, and create, edit and archive memories. Editing a task and using a connector account each wait until you allow them. Jack picks the Isle of Code organization and allows the sign-in.
Back in the chat, Muse reports that qbash is connected. It lists the server's 28 tools, runs a few reads to confirm access, and counts the Tasks and memory folders in the organization. It then offers three starting points: show what is in your qbash Memories, build a qbash Task, or list your qbash connectors.
Read a memory folder
Before recording, Jack created a memory folder called "Qbash Muse MCP Demo" with one document, "MCP Smoke Test", whose content says the memory is proof the MCP is connected. He asks Muse: "Tell me what's inside the Memory folder 'Qbash Muse MCP Demo'".
Muse answers with the one document, its status and version, when it was last updated and by whom, and the text of the document. That text matches what is in qbash, so the connection is good.
Official MCP server covers access tokens, connector approval and the full tool reference. Connect Meta Muse to a qbash MCP Server walks through the same steps for a custom server that packages your own Tasks.
Video transcript
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.