The Model Context Protocol (MCP) is undergoing a fundamental shift. Originally designed for tool calling, it is now expanding to support application hosting—a move that could redefine how AI agents interact with services. OpenClaw.NET, a .NET implementation of MCP, has taken a lead with PR #168, which natively supports MCP Apps. This allows developers to host entire applications within the MCP framework, moving beyond simple function calls to complex, stateful interactions. For the .NET ecosystem, this is a strategic play. It positions .NET as a first-class platform for building AI-native applications, where agents can manage long-running tasks, maintain context, and orchestrate workflows. The implications are broad: from enterprise automation to personal AI assistants, MCP Apps could become the standard for agent-service integration. Developers should watch this space as it matures, potentially influencing how we design and deploy AI systems.
The MCP protocol is evolving from simple tool invocation to full application hosting, a shift exemplified by OpenClaw.NET's PR #168. This marks a significant move for the .NET ecosystem in AI application architecture, enabling richer, more autonomous AI agents.