Infragistics WPF MCP Server: Build WPF Apps with AI
Infragistics released a free, read-only MCP server that hands AI assistants the real Ultimate UI for WPF API: 189 Xam* controls, 5,300+ public classes, 2,600+ documentation topics and both theming systems. The walkthrough covers installing it as a .NET tool, wiring it into GitHub Copilot or Claude Code, and producing a RoyalDark-themed XamDataGrid dashboard from a single prompt.
Key points
- Install with dotnet tool install -g Infragistics.Wpf.Mcp --prerelease; without the flag NuGet reports the package as not found.
- The server needs the .NET 10 SDK, ships all its data inside the package and runs offline with no license key or API key.
- Nine read-only tools cover component lists, API references, docs search, project scaffolding, theme steps, theme resources and palettes.
- Configuration lives in .mcp.json: "servers" for Visual Studio and VS Code, "mcpServers" for Claude Code, or dnx [email protected] --yes.
- The XAML compiler does not validate enum values, so a wrong value such as LabelIcon instead of LabelIcons builds fine and fails at window load.
- Ask the assistant for member filters (for example only the XamCategoryChart YAxis members); 12 of its 16 API lookups used one.
Infragistics has released a free, read-only MCP server for Ultimate UI for WPF. Installed as a .NET tool (Infragistics.Wpf.Mcp, still beta, so --prerelease is required on the .NET 10 SDK), it bundles 189 Xam* controls with their xmlns namespaces and NuGet packages, 5,300+ public classes with properties and enum values, 2,600+ documentation topics and both theming systems, exposed through nine tools an assistant calls while it works.
Wire it into GitHub Copilot (agent mode in Visual Studio or VS Code) or Claude Code with a small .mcp.json entry, then prompt. In the authors' demo one request produced a XamDataGrid dashboard and a XamCategoryChart in the RoyalDark theme; the assistant made 36 lookups, 34 of them before writing any file, and searched the web zero times.
Real-world use
- A WPF team adding an Infragistics grid, chart or scheduler to an existing line-of-business app, where wrong xmlns URIs and property names break the build.
- Onboarding a developer who does not yet know XamDataGrid's filtering, summary and group-by settings well enough to write them by hand.
- Generating a themed dashboard skeleton (grid plus chart in RoyalDark) before the real data source and view models are ready.
- Reviewing AI-written XAML in a code review, using the same API reference the assistant was grounded in.
Why it matters
Third-party control APIs are far too large for a model to memorize, so grounding the assistant in the real registry replaces plausible-looking XAML with code that compiles and loads. Because everything is bundled in the tool, the work also stays local instead of being sent to a vendor service.