Wpf Dev Pack Mcp
Expose WPF Dev Pack knowledge topics from a local dotnet-with-claudecode clone so agents write correct Windows desktop UI code.
Overview
WPF Dev Pack MCP is an MCP server for the Build phase that serves WPF Dev Pack knowledge topics from your local dotnet-with-claudecode clone to AI agents.
What is this MCP server?
- NuGet package WpfDevPackMcp v0.1.3 with stdio MCP transport
- Requires local clone path via WPFDEVPACK_REPO_PATH or /wpf-dev-pack:set-repo-path
- Knowledge source: christian289/dotnet-with-claudecode GitHub repository
- Serves topic-oriented WPF Dev Pack content to agents—not generic .NET docs
- Targets AI-assisted Windows desktop development workflows
- NuGet package WpfDevPackMcp version 0.1.3
- Required environment variable WPFDEVPACK_REPO_PATH for knowledge source path
- Server schema 2025-10-17; registry NuGet v3 index
Community signal: 36 GitHub stars.
What problem does it solve?
Generic LLM answers miss your curated WPF patterns unless the agent can read your dev pack repo reliably.
Who is it for?
Indie Windows developers using AI assistants who maintain the dotnet-with-claudecode knowledge repo for WPF.
Skip if: Web-only SaaS stacks, macOS/Linux UI projects, or teams without a local WPF knowledge clone.
What do I get? / Deliverables
Your agent queries topic-aligned WPF guidance from a local knowledge source through MCP instead of guessing APIs.
- Agent-queryable WPF Dev Pack topics from your repo path
- Reduced XAML and control-pattern hallucinations during implementation
- Repeatable desktop dev sessions grounded in your knowledge base
Recommended MCP Servers
Journey fit
Desktop WPF implementation happens in Build when you are actively coding UI, not during launch SEO or ops monitoring. frontend covers WPF views, controls, and XAML patterns served as agent-readable knowledge from the dev pack repo.
How it compares
Local WPF knowledge MCP over NuGet, not a cloud docs CDN or cross-platform UI framework skill.
Common Questions / FAQ
Who is WPF Dev Pack MCP for?
Solo builders on WPF who want Claude Code or similar agents to read their Dev Pack topics from a cloned knowledge repository.
When should I use WPF Dev Pack MCP?
Use it during Build while implementing views, bindings, and desktop patterns where your dev pack encodes team-specific WPF rules.
How do I add WPF Dev Pack MCP to my agent?
Install WpfDevPackMcp from NuGet, configure stdio MCP, set WPFDEVPACK_REPO_PATH to your dotnet-with-claudecode clone (or use set-repo-path once), then restart your MCP client.