Markus Lippert is working for COSMO CONSULT (cosmoconsult.com) as a Team Manager and technical lead for COSMO Alpaca.
Born near Ulm in Germany, Markus got his master's degree in computer science and started as a developer for Business Software and .NET. After different positions with development and operations tasks, Markus became Team Manager at COSMO CONSULT.
He is blogging on lippertmarkus.com, where he writes about DevOps, Windows Containers and cloud-native technologies, but also tooling like Visual Studio Code. His other focus is Azure, mainly around container orchestration and automation.
When Markus isn't busy trying out new technologies, he also loves to work on his personal development by doing sports, hiking or reading.
Hosted session(s)
GitHub Copilot like other agentic tools becomes dramatically more powerful when it can interact with real systems through MCP tools and servers. There already are MCP integrations for platforms like GitHub, Azure DevOps, AL and Business Central — but what about your own APIs?
In this session, we explore how to automatically generate MCP tools and servers for VS Code directly from OpenAPI specifications. You’ll learn how to expose any REST API — including internal or proprietary ones — to Copilot in an automated, structured, secure, and maintainable way. By generating your own MCP server, Copilot can query real data, act on your systems, and become domain-aware.
We’ll cover the basics of MCP tools and servers in VS Code and how Copilot uses them to reason and act, then dive into the core building blocks: OpenAPI specifications and client generation tools. In a live demo with a C# Web API, we’ll generate a complete MCP tool/server from an OpenAPI spec and plug it into VS Code so GitHub Copilot can use it immediately. We will also experiment a bit with the recently announced MCP Apps capability that adds UI interactivity.