Unlocking the Future of DevOps with Codeglide.ai’s Kumar Chivukula
Codeglide.ai, a subsidiary of Opsera, is co-founded by Kumar Chivukula and focuses on an AI-powered DevOps platform to improve software delivery. MCP servers are crucial for context-aware interactions, and continuous MCP servers adapt to changes in models and APIs. The platform supports full-scale MCP server lifecycle management and integrates with GitHub for secure development. The growing demand for AI integration highlights the market potential for MCP-based infrastructure.
Transcript
Hey everyone. Welcome back here to Textron tv. My next guest is he's been with us before.
New comp, not new company, new product. We're gonna talk today, but let me introduce you to Kumar Chico. ai, which is actually a subsidiary of Sera Kumar.
First of all, welcome back to Text Drunk tv. It's great to have you on here. First of all, thank you for your time, Ellen, and uh, great, great to connect with you again and, uh, thanks for your time.
Always. Alright, Kumar, I, I feel like we need to bring this along chronologically, if you will. Yeah.
So first there was up Sarah. Yes, right? You're one of the CE uh, one of the co-founders of of ops.
com coverage for Yeah. Since you launched. Yes.
I remember when you, you know, you're a new company, but, uh, ops is a DevOps DevSecOps platform, correct? Yes. Okay, so now that we've got that established, what is Code Glide?
Yeah, so let me give you a, first of all, thank you once again. So lemme give you a little bit of background of ops just to quickly, we are a, a AI powered DevOps and dev platform, where in which we meet the customers where they are protect investment. Our vision is to enable empower enterprise companies to make the software delivery faster, better, secure, which we are still sticking to the vision a goal, and we are been making good progress there.
And, uh, we launched the VA features last year and, uh, called Hummingbird ai and which is where we revamped, uh, some of the AI capabilities and, uh, launched it last year and, uh, last few months as well. So as part of the AI transformation, we ran into a stumble block, which is, uh, how can we convert our APAs into MCP servers? So that, which is the why MCP server is important in the first place.
As you, if we take a step back, most of the data is sitting in a backend and those data has been accessed by APAs, good old APAs, right? Those APAs are not designed for AI or LLL, not, they're not context aware, no memory, and then they're not designed for, uh, intent. And, uh, they, they basically, like APAs, you have to write a special blue code to connect with LLMs.
As you know, LLMs are changing every week, almost every, every month. So it's hard for enterprises to connect the data expose to APIs, to LLMs. And that is where Atropic release the, uh, MCP model context protocol.
And this is catching right now because model context protocol is another layer that is coming and it's providing the memory intently aware and also context aware so that citizen developers are the business analysts, business users can interact with the data much more efficiently as opposed to going to the API and engaging a bunch of our blue code in between. And as a result, every company, every enterprise, they have to not abandon NP APIs A ps EPAs will continue to stay, but they introduce another layer. MCP servers.
We struggled our way into creating initially, and because of the way the tools are not available, market is not matured enough to even enable that. We saw an opportunity, we struggle to that. How can we enable an enterprises in the same format where we can, where we can create our own, our own MMCP server.
And more importantly, how can we offer a full scale MCP server lifecycle platform? It's not so much with creation of MCP server. How can we make sure that every time the AP change and secure we create, create the CP server securely, make sure the lifecycle is managed or end-to-end from the time inception to the delivery of the CP server, connecting to the model, making sure that enterprises can be ready with the ai.
That's the intent. We hand that launching the code later ai. So that's the journey and story so far in the last few months.
I love it. And thank you for that in depth sort of, uh, explanation here. So looking at the material, listening to you look from where I sit, it's amazing MCP, right?
Uh, Andro came out with MCP, I think it was just in January. Here we are in August and it's already like the defacto standard for how agent interaction and agent API interaction works. What I'd like to understand about Code Glide is what, you know, everybody seems to be putting on an MCP server, right?
Yes. We're hearing every day that this, this one, that one. What, what, what makes Code Glide unique?
You, you claiming it's the first continuous MP MCP server. Uh, and it's a platform, not just a server. Yes.
What do you mean there? Yeah, great question. So if you take a step back, yes, every company public APAs, they will create, they have to create that one another form factor.
As I mentioned, APAs are not going to go away. You have to have expose A MCP to interact with models. Whatever you're interacting with the APAs, we'll continue to stay unless you re reformat reprogramming.
It's like a cloud migration. If you take analogy of cloud migration and when you, when the cloud came into the foray and then AWS Azure GCP people started moving the data center applications into cloud thinking that it's automatically solve the problem. If you don't refactor them, if you don't and uh, redesign them to the cloud, you'll end up taking a huge bill and you're paying this huge tax and penalty.
Same thing with the A Ps. You cannot expect the APAs to connect to the models and expect, put a glue code and expect it to work. It'll break every time a model changes, it's gonna break.
So that's the reason we calling it a continuous MCP server because you make a change to the model, you make a change to the API, you make a change to the automatically MCP server gets automatically created. You don't have to worry about it. It's not a one-time creation.
It's ongoing creation. And the second thing is why we are different. We are offering a secure m server at scale as a enterprise company, you're not only exposing APIs outside, but also internally as well.
7 billion APAs exist in the market. Not all of them are actively used. And, uh, an average enterprise for 10,000 people, we see anywhere between 10,000 to 12 15,000 APAs that they serve today.
Again, they have a degrees of variation. About about one fourth of them are internal APAs because the applications internally they interact the data with with their own internal application, sales, marketing, engineering and uh, legal hr so on. So finance and so on, so forth.
They have to be in a position to, uh, include the A-P-H-S-M-C-P server to extract the value of the data through ai, gender to AI through models that they have. As a result, they need to have a platform. They can just continue to create a one one micro one MP server.
It's API to MCP server need to be mapped as a result. The problem is not about one time activity, it's ongoing activity. We are offering a full scale MCP server platform, lifecycle platform as a result.
Enterprises can take it by the way, developers can try it out code do AI today. They can create five CP server for free, no strings attached. All they have to do is connect with GitHub.
We built on GitHub ecosystem. There is another reason why it is unique because GitHub has about four 40 million repos today outta them. Like about 10 to 15% of them are APIs.
Repos, like if we do the map, about 50 to 60 million repos are sitting there in a p. They have to convert it into MCP servers. It's not gonna happen in or in a single day.
Even if you try to do it, it's ongoing activity. That is where we want to tap into it. Reach out to developers, helping enterprises with full scale MCP lifecycle platform so that they can manage it continuously without throwing consultants glue code and wasting the time and worrying about the, whether it's gonna work or not.
So our agent framework inside the MCP server, last but not least, we, most of the APAs are not written properly. They're written very poorly. 1.
They don't have a documentation and they don't have a swagger doc swagger information. Sera, in this case code light that we created. We with the agent approach, it automatically features the latest open API and creates a swagger and runs the security scanning.
Ensure that no secret keys, passwords enabled, and also create, look for the, uh, any vulnerabilities and then go through the whole process. Create the MCP server instantaneously, and imagine that if you don't have a code line, it would take any smart developer about two, three days to create amc, an MCP server to maintain that. It takes even more time.
And if to make it work with the model, it take additional resources and time and tax. So just to recap, we built on a hundred percent UB ecosystem and we building a secure MCP servers at scale. And the third one is it's a continuous thing.
And the last, but not least, people don't have to worry about whether my API documentation is there. How do I make sure that the APIs, the basic foundation is available? We will help enterprises to fix the gap that is already created by other people because it's been 15 years in APIs that in the market.
And then, uh, you see, if we go back and look at the history lot people don't even have an inventory. And we can also go the discovery inventory and then extend the, our goal is to create a marketplace where enterprises can manage the internally and externally as well. So we, we have an, we have a plans, we can talk about it subsequently.
I love it. I think another Kumar, again, a great explanation there. Um, you know, I didn't realize the scope of how much as we as we move, I mean we call it the API economy, but it's really gonna be moving to an MCP agent, AI economy and all, all of these, all the dollars time code that was, that was put into, you know, these APIs.
Yes. And, and, and, you know, uh, the connectors for them and everything, we're gonna have have to, it's a huge undertaking. A huge undertaking.
Absolutely. Because it's not going to be, like I said, it's uh, the problem is monumental, right? The 'cause even APAs are growing even in the economy and then basically the con they continue to be there.
The tam that based on what the research is, MCP based a PA infrastructure is about 45 to $60 billion. And uh, when all said and done because of the agent play area, generative AI is fueling this economy and fueling this opportunity because it's a race, right? Every enterprise, they have to find a way to, uh, expose the data, get the value of the data and how be competent when the market and be able to get the answers instantly.
That's the expectation now. And to do achieve that, you have to be meet the models where they are, expose the data in a secure way, ensure that your data is not traversing without writing the blue code. 'cause how do we achieve that?
That's where we've thought about how can we help enterprises and the developers to achieve things faster? The enterprises running in the production and the non-production developers, meeting them at the ideal layer, help them create it, test it, ensure that their code and then their activity has been validated. So when they push the code to the non-product production or get to the non-product production, it automatically available for them to use it Through it.
ai is a website, is the website as well. So people want to get more information they can go right there. Yeah, yeah.
Basically there are two, we are two offerings. One is SaaS offering for somebody wanna play around with it. Any public repo, we just take it.
We, by the way, we also, for the just sake of, uh, our testing, right, we created a bunch of 2030 prominent, uh, like GitHub, Salesforce, and uh, you give Google Maps and, uh, Stripe and Notion bunch of other things. And the workday, we created those APAs to MCP servers. We left it there for people to consume it, just to build the confidence.
And it is available to SaaS up to five MCP servers. Or we also have GitHub Marketplace GI Access Marketplace, where enterprises don't want to expose any of the data to, uh, code light. They can download it, put it out there exactly the same steps, but instead of SaaS, they can do it OnPrem and their on-prem or GitHub ecosystem using GitHub login and GitHub actions.
And the GitHub advanced security secret scanning. So everything's built around GitHub so that they have a high degree of confidence of testing internally or testing public repos externally as well. So we give the public and favor combination so they can consume it both ways for free.
They up to five M MCP servers knows things attached. They can keep it for forever. Really.
Yes. Very cool. Excellent.
I'm, I'm gonna be interested to see how this catches on in there because, so I haven't seen this model Yes. Before for, so we, as I said, we cover a lot of MCP, but Because we, we ran a unique problem because our, we, we are DevOps DevSecOps, we have 150 plus integrations. How can we expose these MCP servers in, in a secure way?
When we stumbled upon it, we ran and we ran, we discovered this problem in a hard way. And as soon as we discovered the problem, we realized that how can we help enterprises to achieve the same goal that we achieved? Excellent.
All right, Kumar, you know, we haven't been on in a while, so I'm glad you're coming on and we, and you're coming on regarding this new product Code Glide ai. Don't be away so long. Come back and keep us posted.
Yeah, Yeah, absolutely. Thank you Aaron, for your time and opportunity. ai, uh, get a market, download this, uh, GitHub actions of code led ai, test it out, provide the feedback, and I just, uh, we want you to create as many MCP service as possible and put it on marketplace.
Thank you. I love it. Kumar Chila, co-founder, CEO of Code Glide ai and upstairs as well.
ai and uh, thanks again for all you do. We're gonna take a break here on Textron.