Content
# wpf-mcp
MCP server for **Infragistics NetAdvantage for WPF** — component registry, XAML namespace lookup, full API reference with property types and enum values, and keyword search across 7,000+ types.
## Tools
| Tool | Description |
|---|---|
| `list_wpf_components` | List all 192 Xam* controls with canonical XAML namespace URIs, NuGet packages, and descriptions. Always call this first before writing XAML. |
| `get_project_scaffold` | Generate ready-to-run `dotnet new` + `dotnet add package` + `dotnet restore` commands and xmlns declarations for a new WPF project. Pass component names resolved via `list_wpf_components`. |
| `search_wpf_api` | Search across all 7,000+ types by keyword — matches type names, summaries, and member names. Use when you don't know the exact type name. |
| `get_wpf_api_reference` | Full API reference for any type: properties with types and enum values, events, methods, and inherited members grouped by base class. |
## Requirements
- **Node.js** ≥ 18
- **.NET 8 SDK** — required for the first-time build
## Setup
```bash
git clone <repo>
cd wpf-mcp
npm install
npm run build:all
```
`build:all` downloads Infragistics NuGet packages, extracts type metadata via reflection, merges with XML docs, and compiles the server. Takes 2–5 minutes on first run (NuGet restore), fast after that.
## Claude Desktop configuration
Add to `claude_desktop_config.json`:
```json
{
"mcpServers": {
"infragistics-wpf": {
"command": "node",
"args": ["C:/path/to/wpf-mcp/dist/index.js"]
}
}
}
```
## Data pipeline
```
NuGet packages (26.2.x)
├── *.dll → C# TypeExtractor (reflection) → nuget/type-info.json
│ (base types, property types, enum values)
└── *.xml ─────────────────────────────────┐
↓
build-api.ts
↓
src/data/api/*.json (7,082 type files)
src/data/namespaces.json (192 Xam* controls)
src/data/search-index.json (search index)
```
## npm scripts
| Script | What it does |
|---|---|
| `npm run build:all` | Full pipeline: NuGet restore → type extraction → API build → TypeScript compile |
| `npm run generate` | API data only (no TypeScript compile) |
| `npm run generate:types` | C# reflection extractor only → `nuget/type-info.json` |
| `npm run build` | TypeScript compile only (requires `src/data/` to exist) |
| `npm run inspector` | Launch MCP Inspector for interactive testing |
## Development notes
- SDK: `@modelcontextprotocol/sdk` v1 (v2 releases ~July 28 2026 with breaking package renames)
- Zod v3 schemas — upgrade to v4 when migrating to SDK v2
- All tools are read-only (`readOnlyHint: true`, `openWorldHint: false`)
---
<details>
<summary><strong>Architecture</strong></summary>
### Why this approach
Infragistics WPF NuGet packages ship two files per assembly:
- `InfragisticsWPF.*.dll` — the actual binary
- `InfragisticsWPF.*.xml` — compiler-generated XML doc comments (`<summary>`, `<param>`, etc.)
The XML files give you descriptions but nothing else — no property types, no enum values, no inheritance. The only way to get that is reflection on the DLL. That's also what Infragistics' own documentation tool (Innovasys Document! X) does internally before generating their live help site.
### Build pipeline
```
NuGet packages
├─ *.dll ──► scripts/type-extractor/Program.cs (C#, reflection)
│ Loads all Infragistics DLLs into one AssemblyLoadContext
│ Walks every public type: base type, properties with types,
│ enum members, nullability
│ Output: nuget/type-info.json (36k entries, compact JSON)
│
└─ *.xml ──► scripts/build-api.ts (TypeScript)
Parses XML docs per assembly using split-based chunking
(avoids catastrophic regex backtracking on multi-MB files)
Builds a Map<typeFQN, members> per file (O(n), not O(n²))
Merges with type-info.json to attach typeName/enumValues
Walks __baseType chain with cycle guard for inherited props
Writes async parallel: src/data/api/{TypeName}.json (7k files)
Also writes: src/data/namespaces.json, src/data/search-index.json
```
### Runtime data layout
| File | Size | Loaded | Purpose |
|---|---|---|---|
| `src/data/namespaces.json` | ~50KB | At startup | 192 Xam* control registry |
| `src/data/search-index.json` | ~5MB | At startup | Compact index: name + summary + member names |
| `src/data/api/{Type}.json` | ~5–15KB each | On demand | Full member details per type |
The search index is loaded once and kept in memory — search never touches individual type files. `get_wpf_api_reference` loads exactly one file per call.
### Key design decisions
- **No reflection at query time** — all reflection happens at build time. MCP responses are pure JSON file reads.
- **`type-info.json` is gitignored** — regenerated by `build:all`. Users need .NET 8 SDK for first build.
- **`src/data/` is gitignored** — regenerated from `type-info.json` + NuGet XMLs by `build-api.ts`.
- **Inheritance enrichment** — `enrichWithInheritance()` walks `__baseType` chains and copies parent properties to child entries with a `declaredOn` label. This is why `XamDataGrid` shows 74 properties even though it declares very few directly.
- **`internal` filter** — members with `summary === "internal"` are stripped. These are public DLL members that developers wrote placeholder docs for but aren't part of the public API surface.
</details>
