Usage is Visual Studio with the target repo open on Windows [on a specific branch]: concurrently an AI updates the same repo remotely (Linux). Git's pushed and a local-watcher|remote-script (securely) updates the Windows clone; thereby triggering Visual Studio's nCrunch integration. All of this is arranged. NCrunch "just works".
I expected nCrunch MCP http to connect just as the local [stdio?] would within VS|Rider IDE integration but the connection reports no active sessions.
Connecting to an nCrunch [http] instance via cmdline instantiation of NCrunch.MCP.exe (this is the root irritation) reports different test counts (more) and all passing (while VS's integration has multiple fails across multiple projects).
Am I missing something or is this intentional/constrained design? Not the local vs CI|remote difference, obviously. nCrunch facilitating a third leg convergence isn't new but an opaque headless divergence from the IDE isn't quite cutting the mustard.
FWIW nCrunch's speed and accessible visualization is worth more than ever under AI acceleration so, even if I'm a little late to the MCP effort, it's nonetheless welcome. Thx for holding fort vs bulk licencing. Appreciated.