Documentation
These pages are rendered straight from the repository's markdown on every push, so they never drift from the code they describe.
What the server is, how to install and register it, the full tool contract, and how to fix the problems you are most likely to hit.
What it wraps and what it doesn't, the eighteen tools and two documentation resources plus the error-catalogue resource family at a glance, honest prerelease status, secret hygiene, and the engine pin.
2 · GUIDEThe dotnet tool install command, the .mcp.json registration snippet, and what run_suite additionally needs on PATH.
3 · REFERENCEEvery tool's parameters, result shape and notable behaviours — plus the two vendored-document MCP resources.
4 · GUIDECLI pin/version mismatches, Docker daemon unavailability, timeouts and cancellation, and validation timeouts.
How this repository is run.
Live evidence runs against the real vouchfx CLI, a real Docker engine, and real sample suites.
A live, uninterrupted validation run of every vouchfx-mcp tool and resource against the real vouchfx CLI, a real Docker engine, and a real sample suite — including graceful-teardown evidence.
VALIDATIONVerifies the MCP's graceful-shutdown grace stays safe against the current engine pin, on a real Docker topology — the mandatory gate before every ENGINE_PIN advance.
Where the rest of the vouchfx fleet lives.
The architecture blueprint, the YAML DSL specification, and the language reference this server vendors.
HUBThe community provider registry — every step type list_step_types/describe_step_type report comes from the Core set this catalogue governs.
SAMPLESFour production-shaped applications proving the same engine end-to-end, in four stacks.
TELEMETRYThe optional, privacy-allowlisted run-metadata aggregation service.