wpf-mcp

MCP server for Infragistics Ultimate UI for WPF — component registry, XAML namespace lookup, full API reference with property types and enum values, keyword search across 6,900+ types, and named-theme setup with palette re-coloring.

Distributed as a NuGet dotnet tool, Infragistics.Wpf.Mcp — currently in beta (0.1.0-beta.0). From the first stable release it will also be listed in the MCP Registry as io.github.Infragistics-Developer-Tools/wpf-mcp.

Tools

All tools are read-only (readOnlyHint: true, openWorldHint: false) — none of them modify your project, filesystem, or any external system.

Installation

Requires the .NET 10 SDK or newer (Windows, macOS or Linux) — dotnet tool install and dnx are SDK commands, so the .NET 10 runtime alone is not enough. All Infragistics data ships inside the package and nothing is downloaded at runtime.

Beta: the package is a prerelease, so every command below needs --prerelease or an exact @0.1.0-beta.0 version — without one, NuGet reports the package as “not found”.

Option A: global install (gives you a wpf-mcp command on PATH)

dotnet tool install -g Infragistics.Wpf.Mcp --prerelease

Update with dotnet tool update -g Infragistics.Wpf.Mcp --prerelease, remove with dotnet tool uninstall -g Infragistics.Wpf.Mcp.

Option B: run on demand with dnx (downloads and caches the package on first use, nothing to install or update by hand)

dnx [email protected] --yes
# or always the newest prerelease:
dnx Infragistics.Wpf.Mcp --prerelease --yes

Check that it starts. Run wpf-mcp (or the dnx command above) in a terminal. It prints a line like this to stderr and then waits for an MCP client on stdin:

Infragistics WPF MCP server 0.1.0-beta.0 ready (data: Infragistics 26.1.21, built )

Press Ctrl+C to stop it. To try the tools without an AI client, open it in the MCP Inspector: npx @modelcontextprotocol/inspector wpf-mcp.

MCP client configuration

Visual Studio — add .mcp.json next to your solution (or %USERPROFILE%\.mcp.json for all solutions):

{
  "servers": {
    "infragistics-wpf": {
      "type": "stdio",
      "command": "wpf-mcp"
    }
  }
}

VS Code (Copilot) — add to .vscode/mcp.json:

{
  "servers": {
    "infragistics-wpf": {
      "type": "stdio",
      "command": "wpf-mcp"
    }
  }
}

Claude Desktop — add to claude_desktop_config.json:

{
  "mcpServers": {
    "infragistics-wpf": {
      "command": "wpf-mcp"
    }
  }
}

Claude Code — from a terminal:

claude mcp add infragistics-wpf -- wpf-mcp

To use dnx instead of a global install, set "command": "dnx" and "args": ["[email protected]", "--yes"] (Claude Code: claude mcp add infragistics-wpf -- dnx [email protected] --yes). Add "--debug" to args for any client to log every tool call/response to wpf-mcp.log in your system temp folder (override with the WPF_MCP_LOG environment variable) — see Troubleshooting.

To run from a source checkout instead, build it first (see DEVELOPMENT.md) and point command/args at dotnet and path/to/wpf-mcp/server/bin/Debug/net10.0/wpf-mcp.dll.

Troubleshooting

• infragistics.wpf.mcp is not found in NuGet feeds — the command is missing --prerelease (or an exact @0.1.0-beta.0 version); see Installation.
• Settings file 'DotnetToolSettings.xml' was not found in the package — the active .NET SDK is older than 10 (check dotnet --version; a global.json in the current folder can pin an older one). Install the .NET 10 SDK.
• Which Infragistics version is the data from? The server prints it to stderr on startup: Infragistics WPF MCP server 0.1.0-beta.0 ready (data: Infragistics 26.1.21, built ). Every release regenerates the data from the version pinned in nuget/WpfDocs.csproj.
• Run the server with --debug (add it to your MCP client config’s args, see above) to log every tool call’s input/output/timing to wpf-mcp.log in your system temp folder — useful for reproducing an agent’s exact tool-calling sequence after the fact. The exact path is printed to stderr on startup, and can be overridden with the WPF_MCP_LOG environment variable.
• wpf-mcp is not found after dotnet tool install -g — the global tools folder (%USERPROFILE%\.dotnet\tools on Windows, ~/.dotnet/tools elsewhere) is not on the PATH of the process that launches the client. Restart the client, or use the full path as command.
• A tool call succeeded but the answer looks wrong or a control seems missing — this is usually stale/outdated data from Infragistics’ own NuGet package (summaries, base types) rather than a bug in this server. Cross-check against the pinned version above before assuming the MCP itself is at fault.
• A tool returns “no topics found” / “no themes found” for everything on a source build — the data pipeline didn’t complete. Re-run npm run build:all and read the output; it either reports real counts or aborts with a 🚨 banner saying exactly what’s missing. Published packages are validated against these counts before release, so this can’t happen with a NuGet install.

Contributing

Build pipeline, data updates, adding tools, versioning and the publish process are documented in DEVELOPMENT.md. The published C# server lives in server/. A TypeScript implementation in src/ reads the same generated data; it is frozen and not published, and newer behavior (such as the get_wpf_api_reference size guard) exists only in the C# server.

License

MIT