VFX-E-1401¶
Title¶
EngineCliUnavailable
Explanation¶
The pinned vouchfx CLI is missing, version-mismatched, unparseable, or not launchable. Shared by all
five CLI-backed tools — list_step_types, describe_step_type, plan_coverage, scaffold_suite, and
run_suite — because the condition and its remediation are identical for every one of them: the
environment this server orchestrates through is not available.
Common causes¶
- The
vouchfxCLI is not installed, or not onPATHfor the account runningvouchfx-mcp. - An installed CLI's version does not match this server's own
ENGINE_PIN. - The CLI is installed but not launchable (a corrupted install, a missing runtime dependency), or its version output could not be parsed.
list_step_typesordescribe_step_typeonly: the CLI could not load a configured external provider location (engine v1.2.0 and later), for example aVOUCHFX_PROVIDERSentry naming a directory that does not exist, sovouchfx list --jsonexited 3. The version check passes in this case, and the other CLI-backed tools report the same condition under their own codes.
Fixes¶
- Install the
vouchfxdotnet tool at the version named in this repository'sENGINE_PINfile:dotnet tool install -g vouchfx --version <pinned-version>. - Run
vouchfx --versionyourself to confirm it is onPATHand launches successfully. - If a different CLI version is intentionally installed, this server's
ENGINE_PINneeds advancing — a maintainer/release task, not something a single call can work around. - Run
vouchfx list --jsonin this server's environment. If it reports a provider error, correct or unsetVOUCHFX_PROVIDERS, or repair~/.vouchfx/providerswithvouchfx providers uninstallandvouchfx providers install; reinstalling the CLI does not help. A changedVOUCHFX_PROVIDERStakes effect only after this server restarts.