you want the standalone LSP host outside the bundled VS Code extension
you are wiring editor integrations yourself
you want to debug the server independently from client middleware
What it exposes
The tool packages the AXSG server process and gives editors a stable command-oriented deployment path instead of requiring them to embed the shared engine directly.
It is the correct artifact when you want a reusable LSP host rather than a bundled editor experience.
Typical scenarios
local editor experimentation without the bundled VS Code extension
alternative editor integrations that speak standard LSP
automated editor or language-service smoke testing
debugging transport, request handling, or project-loading behavior outside the VS Code client
How it differs from the VS Code extension
The tool gives you the server process and transport surface.
It does not give you:
VS Code activation rules
status bar integration
projected inline-C# middleware
editor-specific fallback behavior
Those remain in the VS Code extension because they are client responsibilities.