This New Roo Code Memory MCP IS INSANE (AND FREE)

Brief Summary

The video discusses the creation and implementation of a custom Memory Bank MCP (Multi-Context Processor) server to improve context sharing between subtasks in AI development, particularly within the Roo Code environment. The creator expresses dissatisfaction with the original implementation of the Roo Code memory bank and demonstrates how to build a more efficient MCP server using Klein and the sequential thinking MCP as a base. The new MCP server is designed to ensure that all subtasks have access to the overall context of the main task, addressing a key limitation in current AI task orchestration. The creator also shares the MCP server on GitHub, providing a valuable tool for the AI development community.

  • Creation of a custom Memory Bank MCP server for improved context sharing.
  • Implementation using Klein and sequential thinking MCP as a base.
  • Addresses the issue of subtasks lacking overall context in AI task orchestration.
  • Sharing the MCP server on GitHub for community use.

Why Roo Code Memory Bank Needs Improvement

The creator expresses reservations about the existing Roo Code memory bank implementation, particularly its use of custom instructions. Dissatisfied with its implementation, the creator decided to develop a custom MCP server.

Creating My Own Memory Bank MCP Server

The creator explains the process of building a custom MCP server. Using the sequential thinking MCP server as a base, the creator integrates the functionalities of the Roo Code memory bank. This involves leveraging third-party APIs and providing specific GitHub links to Klein, instructing it to create an MCP server that accomplishes the desired tasks.

The Simple Prompt That Built The Entire MCP

The creator shares the prompt used to instruct Klein in building the MCP server. The prompt involves cloning both the sequential thinking MCP and the Roo Code memory bank projects into a new directory. The key instruction is to implement the Roo Code memory bank using the methodology of the sequential thinking MCP, effectively creating an MCP version of the memory bank.

How I Got Klein To Build The MCP In 5 Minutes

The creator details the speed and ease with which the MCP server was created using Klein. Within minutes, Klein generated the project with minimal adjustments required. The primary modification involved ensuring that the necessary settings were added to the Klein settings to ensure proper functionality.

The Context-Sharing Problem This MCP Solves

The creator explains the problem that the Memory Bank MCP solves, which is the lack of overall context in subtasks when breaking down a larger task. The Roo Code memory bank aims to fix this by ensuring each subtask has the necessary context. The creator's MCP server seeks to replicate this functionality with a more efficient implementation.

Testing The Memory Bank MCP With Roo Code

The creator tests the newly created Memory Bank MCP to ensure it functions correctly. A website-building prompt is used to test whether the MCP can split the task into subtasks and create the necessary files. The memory bank functions by writing down all prompts into a document and feeding them to the next prompt.

Setting Up The Memory Bank In Klein Settings

The creator integrates the Memory Bank MCP into Klein by adding it to the custom instructions for all modes. This ensures that the memory bank is accessible and functional within the Klein environment. The creator emphasizes the importance of keeping the custom instructions box dedicated to specific tasks, highlighting the value of the MCP server.

Seeing Memory Bank Working In Real-Time

The creator demonstrates the Memory Bank MCP working in real-time. The system creates a memory bank, which is helpful in passing information to each subtask. The MCP writes down the task details, ensuring that every subtask receives the necessary context.

Fixing The "Always Allow" Setting Issue

The creator addresses an issue with the settings, specifically the need to change "auto approve" to "always allow." This adjustment ensures that the MCP functions correctly and consistently.

How This MCP Passes Context To All Subtasks

The creator explains how the MCP passes context to all subtasks, ensuring that each subtask has the necessary information to complete its part of the overall task. By reading the context every time, the MCP solves the problem of subtasks lacking the necessary background information.

Preparing To Share The MCP Server On GitHub

The creator prepares to share the MCP server on GitHub, making it available to the broader AI development community. The MCP server is first shared with the creator's school community before being released as a video.

Using Klein To Push The Code To GitHub

The creator uses Klein to push the code to GitHub, simplifying the process of sharing the project. Klein's capabilities make it easier to manage GitHub tasks, which the creator appreciates due to a dislike for the traditional GitHub interface.

Adding A Readme File For Easy Installation

The creator adds a readme file to the GitHub repository, providing instructions on how to set up the MCP server, including how to configure the settings list.json file. This ensures that others can easily install and use the MCP server.

Final Test Of Memory Bank Working With Subtasks

The creator conducts a final test to ensure the Memory Bank MCP is working correctly with subtasks. The test confirms that the memory bank exists and can be read by the subtasks, demonstrating the effectiveness of the MCP in passing context.

The Holy Quintupelly Of AI Development

The creator expresses excitement about the successful implementation of the Memory Bank MCP, referring to it as the "Holy Quintupelly" of AI development. The ability to have memory and context passed between tasks is highlighted as a significant advancement.

Final Thoughts On Memory Bank MCP Value

The creator concludes by emphasizing the value of the Memory Bank MCP and expressing hope that others will recognize its benefits. The video encourages viewers to explore the GitHub repository and support the creator's school for further learning and development in AI.

Summarize any YouTube video in seconds

Get summaries like this one for any video, in your language, with the free Summ app.

Download on the Apple Store
Get it on Google Play

Transcript

Full transcript of “This New Roo Code Memory MCP IS INSANE (AND FREE)”. Click a timestamp to open the video at that moment. Need another video? Use the YouTube transcript generator.

0:00 Okay guys, so a lot of people have been asking me to cover the R code memory bank. Now this does look like a very interesting project. The only thing that I don't like is number one, how to implement it. I really don't like using my custom instructions on, you know, something like this. Like I just don't like this. And just generally I just wasn't a big fan of the implementation of this. So what I've done basically, and I'll tell you exactly how I did it. I'll show you exactly how I did it is I've made my own MCP server. Now, if you haven't got into this yet, guys, I cannot recommend this enough. Basically, what you can do and it's a very very simple process is you can take something like the sequential

0:48 thinking MCP server, right? So, you take this GitHub and I'll show you my prompt for this, right? and you say right I like this third party API like data for SEO or in this case I wanted root code right uh R codes memory MCP so I just gave it both of these GitHub links I gave it to Klein and I said make me an MCP server using sequential thinking as a kind of base of how to implement the MCP server and R code memory bank on how like what I want the MCP P server to accomplish, right? And that's literally my that was my entire prompt. So, if I just scroll up here, I'll just go here. Literally, just this was my prompt. Start by cloning

1:33 both of these projects into a new directory. On you can just copy this down, guys. It's probably not going to be in the description. Once you've got them both, dissect them. The important thing is the sequential MC sequential thinking MCP is the methodology that I want to implement Rode memory bank. As in, I want to make an MCP version of the R code memory bank. So it works in the same way but as an MCP instead of how it's currently implemented which uses system prompts. And then I just got it to really make sure that it had actually read all of the files, right? Because I didn't believe it and it read all the files and I was right. It hadn't read all of the files. And then it started to create the project and then literally within like 2 to 3 minutes I didn't really change anything. All I did was say you need to add cuz it never adds to your client settings and they obviously need to be in client settings and then I'm done. Right. Literally, it took me

2:20 five minutes to make this. Now, the reason I'm making this, if you don't know, is for RU code boomerang or orchestrate. Now, what this does is it takes one task and it breaks it into maybe 10 tasks, right? Subtasks. But one of the issues this has is that each subtask doesn't have the overall context of the task, right? And that's the problem that this um recode memory bank uh has fixed basically. But like I said, I didn't like the implementation. And so I've hopefully made something that works in the same way but as as an MCP server. Now just to test this guys, I'm going to do a very very quick um like I'll be able to see immediately if this is working or not basically. But even if this doesn't work guys, I'm going to put this video up. The reason

3:05 is is I cannot recommend enough making your own MCP servers and putting them together with system prompts. Right. So actually I just changed my system prompt slightly for Klein. I should have put it here. Did I? Yeah. So now you can put this inside rue custom instructions for all modes. Right. So the I didn't like the fact that rue code memory bank was using this box because this box to me is absolutely sacred. Like I need this box to do exactly what I needed to do. So now we have a memory bank, right? It was actually surprisingly very very easily very very easily implemented. Okay. So, what I'm going to do here is I'm going to just paste this giant prompt in here and I'm just going to let it go and I'm going to see immediately whether it

3:52 works or not. This prompt, by the way, is basically it's just a website building prompt. I just need it to split into subtasks and I need to see whether it's creating the files needed in order to actually run the memory bank. If you don't know, memory bank is actually pretty crude. is basically just writing down all of the prompts so far into a document and then feeding them to the next prompt. Right? There's not really much special going on here, but there we go. Check memory bank status. Of course, it didn't connect. Now, it's connected on client. So, I'm just going to press cancel here. I just realized I didn't actually put this inside um ruse settings, so that's why it didn't work. So, we can control arr c to copy all. Edit global

4:39 MCP. I'm going to paste this, but I need to remember to change change it to is it auto approve or did they did R stop doing that? I think R might have stopped doing that. Try again, please. Uh, it wasn't activated. Let's just double check that this is connected. There we go. Just double double double check because MTP servers are very annoying. So now it should initialize or it should check the memory stank memory memory bank status. If you don't know guys, I always say words the wrong way around. Uh so I almost said stank sank potato or something. I don't even know. Okay. So now you can see look it's now creating

5:26 um a memory bank, right? Which is really helpful in certain cases. Now you can work on this memory bank. You can make it do whatever you want. I'm not sure what it's doing here. I think this might just be from here, right? Okay. I understand the task. Is that what it's writing down? I don't know where it's getting this brief from. I mean, this is more useful than not having this information passed on to every single um subtask, right? Then it goes on to doing its its bit, its other things. Now I need to there's a there's a different word here that they use. Is it always allow? Yeah, I need to change um auto

6:13 approve to always allow, I think. Yeah, always allow. They always do this. I don't know why they can't just use the same bloody word. Why would they change that? Like, it's so annoying to change that. Please ru don't do that. Okay, so the rest of what this is doing is it's basically just doing the rest of the problem that I asked it to do. Okay, so look if this this is really really great. If all of this information is being passed onto every subtask, this actually fixes the problem immediately. Now it might not pass it on this time just because um it's hard to explain but basically the system prompt might not pass it to the

6:58 subtask right because that's the important thing is that this um context always gets passed. So if you think about it what it can do every time is it can read the context. This actually solves the problem guys. I'm going to post this MTP server because I think people are going to find it really really useful. It's going to get posted to my school community first and then later as a video which you're seeing now. Let's actually just push it to GitHub real quick. So if I just go here and say help me push this to GitHub and then I need to actually make the GitHub thing github.com github.com new uh what's that thing called? I think this is fine, right? I I I I'm just

7:45 helping I'm helping them if anything. The hell are they called? RO. How I don't know if I'm doing this right. I don't know if I want to piss anyone off here, but uh Okay. I hope I don't annoy anyone. Help me push this to GitHub. I hope the makers don't mind me doing this. I mean, it's got a specific license, right? It's open source. I think it's totally fine for me to do this license. Whatever. I think it's fine. I'm doing the community service by releasing this. Makes it a lot easier. The way that they were doing it was way

8:31 too complicated. That is what I love about client guys. Like I hate I hate GitHub. It's so much easier for this for client to do it for me. It's actually crazy, right? So, this is now on GitHub, guys. I'll leave a link to the descript in the description to this GitHub. Should be fairly easy to set up. There's no readme file. Make me a reading file, please. And make sure it includes how to set up in a setting list.json file and any other information someone might need. And then it even just re committed my files. That is crazy. Uh, I didn't even ask it to do that. Now I just need to do get push one

9:16 more time. I forget the command though. git push- origin main. Get push- origin main. That should then push the readme file. And now you guys can use this for yourselves as well. And then look at that. This is a subtask. Instantly check memory bank status. It exists. So, it exists. I will now read it. That is actually OP as hell, guys. That's so so cool, honestly. Oh my god. It's going to be more expensive, but it just feels so good to have that memory. That's it, guys. That's the Holy Quintupelly or whatever the hell you want to call it. Thanks for watching, guys. If you're watching all the way to the end of this video, I don't know what

10:01 you're doing listening to me ramble like this, but my god, is this some value. I really hope people actually see the value in this and not just leave me negative comments. Thank you for watching. If you're watching all the way to the end of the video, you're an absolute legend. GitHub for free. Check out the school if you want to support me or if you just want to learn a little bit more about these things. Thanks for watching and peace.

Share

More video summaries