Live tooling for humans and agents

Hot Reload, Hot Design & MCP

Give editors and coding agents the same live, structured control over XAML workspaces.

Explore source
Parent systemXamlToCSharpGenerator
StatusActive
Modules3
RepositoryXamlToCSharpGenerator/XamlToCSharpGenerator.RemoteProtocol

Workspace, runtime, and preview MCP hosts expose semantic queries, preview lifecycle, source-generated hot reload, hot design, studio state, and remote protocol contracts.

  1. 01

    Workspace, runtime, and preview hosts

  2. 02

    Source-generated hot reload

  3. 03

    Hot design and studio state

  4. 04

    iOS and remote transport support

From intent
to working system.

01

Host

The selected workspace, runtime, or preview process owns authoritative state.

02

Describe

Remote protocol contracts expose capabilities and structured resources.

03

Change

Clients update source, preview state, or running generated views.

04

Verify

Diagnostics, lifecycle, and runtime state close the feedback loop.

Adopt this
capability.

Start with the primary module, then add the related packages only when the application needs those layers. Replace VERSION with the current NuGet version.

01 · Install
Terminal
dotnet tool install --global XamlToCSharpGenerator.McpServer.Tool
02 · Use · bash
Terminal
axsg-mcp --workspace /path/to/repo
# Runtime hosts expose hot reload and hot design state.
# Preview hosts support start, update, reload, and stop
# through the shared remote protocol.

Use one layer.
Compose the rest.

Read the module beside the complete system.

The implementation, samples, issues, and release notes stay in the parent repository so module details remain connected to the product architecture.

XamlToCSharpGenerator

Search everything.

Loading the index…

move open esc close

Preparing metadata and full-text search…