Tobias Fenster started as a developer in the 1990s. Holding different positions including Head of Technical Consulting, Head of Development and CTO for multiple Microsoft partners during his career, he is now a Managing Director at 4PS Germany and Chief Engineer at Hilti. He is also a Microsoft Regional Director, holds dual Microsoft MVP awards for Business Applications and Azure and is a Docker Captain.
He is blogging on tobiasfenster.io, where he writes about Business Applications, Docker and Windows Containers, but also tooling like Azure DevOps, Visual Studio Code and infrastructure automation. His other focus is Azure, mainly around container environments and SQL.
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.