In the previous episodes, I talked about my RAG server, why it exists and how it helps me provide context to AIs. But as my experiments progressed, I realized an important point: a RAG server, no matter how well built it is, is not sufficient for a smooth and robust integration with modern AIs. There is a missing building block to connect coding agents to my RAG server. In this article, I will explain: ...
Following the previous episode (/mo5-blog/days/day-6-rag-server/), I wanted to go one step further: deploy my RAG server on the Internet. The goal was twofold: make the server accessible from the outside allow coding agents (Copilot, Augment, etc.) to have a precise context to help with MO5 development (the project is described here: https://retrocomputing-ai.cloud/) Deploying a RAG, but not just an API To connect coding agents with my RAG server, I created an MCP server. It acts as a standardized interface between AI tools (Copilot, Augment, etc.) and my RAG API. ...
If you’ve followed my previous adventures, you know that coding on MO5 is… intense ;) Between tools from another era, hardware constraints that are not always well documented, and different behaviors between emulator and real hardware, I spent quite some time fighting my environment. At some point, I realized something simple: I was spending more time fixing my tools than coding my game, and that is frustrating. The real problem At first, I thought the problem came from the MO5: old machine, strong constraints, makes sense. ...
After building my MCP server, I figured it would be a shame to leave it sitting in a corner. An unlisted MCP server is a bit like a restaurant with no sign out front. It exists, but nobody finds it. 😄 So I decided to publish it in the MCP registries. And as usual… it was “straightforward” 😅 What’s an MCP registry? An MCP registry is a directory of MCP servers. Coding agents (Claude Desktop, Cursor, Augment…) can connect to it to discover and install servers. ...