Building CodexMCP: The Raw Process Behind the Vision

From here on out this blog will be a live, unfiltered look at the process of building CodexMCP—a project that has been brewing in my head for years. This is not just another software project; this is the culmination of 20+ years in telecommunications, IT, and network operations, all wrapped into a single open-source platform designed to unify and simplify ISP operations.
But before we get into what it will become, let’s talk about what this blog is.
The Scratch Pad Approach
You’ll see posts here that are raw, unpolished, and straight from the trenches. They document my thought process as I tackle one challenge after another, piecing this massive system together. This is a live log of what I’m trying, what works, what fails, and what pivots I take based on those lessons.
Some of these posts will be deep dives into the technical weeds—logs, API calls, OpenSearch quirks, VyOS automation, Proxmox scripting, and the entire NLP-driven knowledge base that sits at the core of this project. Others will be high-level reflections on design choices, the evolution of ideas, and how each component interlocks into the broader system. You’ll see the entire journey, warts and all.
The Plan: Build, Tear Down, Rebuild
Right now, I’m in the messy phase—working through problems, logging solutions, and laying the groundwork. At some point, I’ll get CodexMCP to a state that I’m happy with. And then? I’ll tear it all down and rebuild it from scratch.
Why? Because that’s how real, hardened systems are born.
The first pass is discovery. The second pass is refinement. By the time I reach the final phase, I’ll have a complete, step-by-step record of everything: the manual steps, the automation journey, the NLP tuning, and the final polished implementation. What starts as a messy scratch pad will evolve into a comprehensive documentation set—something that anyone can follow to deploy and extend CodexMCP themselves.
The Heart of This Project: Knowledge, NLP, and Automation
At its core, CodexMCP is about making sense of data—connecting logs, alerts, configurations, and human-readable knowledge into a single, intelligent system. The knowledge base (KB) with NLP tuning is the brain behind it all. The system isn’t just about displaying data; it’s about making that data useful, helping operators troubleshoot, automate, and visualize their networks in ways that have never been done before in a unified, open-source ISP operations platform.
The evolution you’ll see here will reflect that mission. It starts with manual steps—building out routers, provisioning VMs, gathering logs—but as the project matures, you’ll see that same process get fully automated, optimized, and documented. Every misstep, every experiment, and every breakthrough is part of that path to full automation.
The Bigger Picture: Why I’m Doing This
I’ve spent decades working across every aspect of telecommunications and IT, from managing massive rural networks to developing monitoring systems that are still in use today. CodexMCP is my way of pouring all that experience into something tangible, something that can push the industry forward.
I’m not building this as a commercial product—I’m building it as a statement. A proof of concept that a truly unified, intelligent ISP operations platform can exist, open-source and freely available for anyone who needs it.
If that sounds like something you want to follow, stick around. Watch as this thing takes shape. And when the documentation is finally polished and complete, know that it came from thousands of hours of real-world testing, failures, and refinement.
This is CodexMCP. Let’s build it.
-Out There Somewhere....
--Bryan Vest