De Vries Will Detail .NET Model Context Protocol Use

A forthcoming session in Orlando will address how developers can bridge existing .NET application logic with AI agents.

Updated on Oct. 13, 2026 in Artificial Intelligence

Bold flat-color editorial illustration featuring geometric navy, red, and cream shapes, representing architectural software interface design.
Marcel de Vries of Xebia will outline methods for integrating existing .NET application logic with AI agents at the Live! 360 event. AI Illustration. Upload story photo >

Live Poll

Do you trust that businesses can safely integrate their internal data systems with AI agents?

Marcel de Vries, CTO at Xebia, will present a technical session on integrating .NET applications with the Model Context Protocol at the Live! 360 event. This guide will focus on architectural design decisions for developers connecting AI systems to legacy software.

Why it matters

Developers increasingly need methods to safely expose existing application capabilities to autonomous AI agents. This session addresses the critical challenge of scaling these integrations without compromising performance.

Engineers are advised to limit deployments to approximately 10 tools to maintain model performance, as scaling to 200 tools can lead to significant degradation. The framework utilizes a discovery mechanism where servers expose schemas for tools, resources, and prompts to clients.

The players

Marcel de Vries

Global managing director and chief technology officer at Xebia with a focus on enterprise architecture and .NET development.

Live! 360

A developer-focused conference series occurring in Orlando that features sessions on .NET, AI, and enterprise software.

The details

The Model Context Protocol acts as a standardized interface, allowing AI applications to communicate with external tools and data sources. Developers construct thin, independently deployable servers that act as a bridge, enabling AI agents to invoke logic within existing legacy .NET services. This modular architecture allows systems to remain decoupled while providing the AI with structured access to internal application functions.

Timeline

  1. October 13, 2026: Article publication date.

The Tech Race

The transition toward agentic AI workflows has spurred a race to standardize how large language models interact with enterprise software. This presentation contributes to a growing body of implementation patterns that attempt to normalize interface protocols across the fragmented .NET ecosystem.

Developers in Orlando and beyond will gain actionable architectural guidance on building Model Context Protocol clients and servers using the official C# software development kit. This session provides a practical template for teams looking to make their .NET applications accessible to AI agents.

The takeaway

The primary takeaway for architects is the necessity of strict tool-set limiting to preserve model performance. Developers should monitor upcoming documentation from the .NET AI community for emerging benchmarks on protocol server latency and resource overhead.

Further reading

For broader trends in model integration and development tooling, review our coverage of Artificial Intelligence.

Source note: This article includes information reported by Visual Studio Magazine.

Live Poll

Do you trust that businesses can safely integrate their internal data systems with AI agents?