vouchfx-mcp

A native vouchfx toolbelt for AI agents.

A local stdio Model Context Protocol server that wraps the packaged vouchfx CLI — six tools and two documentation resources, so an agent works with .e2e.yaml integration-test suites directly, instead of shelling out and parsing console output by hand.

Install & register Tool & resource reference GitHub repository

Wraps the published vouchfx CLI pinned in ENGINE_PIN · current engine release v1.0.0-rc.1 · early prerelease — feature-complete, not yet published to NuGet.org

Everything a call away

Six tools. No shelling out, no scraping output.

Every tool returns a structured result — success or a typed failure — so an agent never has to parse free-form text to know what happened.

validate_suite

Validates an .e2e.yaml suite against the engine's JSON Schema, without running it. Runs isolated in a killable child process.

list_step_types

Lists all 25 Core provider step types, grouped by family — derived straight from the embedded schema.

describe_step_type

Returns one step type's full required/optional field contract.

search_docs

Free-text search over the vendored language reference and recipes, with deep links to vouchfx.io.

run_suite

Runs a suite through the installed vouchfx CLI and reports its taxonomy-faithful verdict — pass / fail / environment error / inconclusive.

explain_run

Diagnoses a completed run purely by reading its JSON Lines event stream — never re-running anything.

Plus two documentation resources

The engine's own docs, vendored byte-exact.

Read directly as MCP resources, or reach the same content through search_docs.

RESOURCE Language reference — every common step field and step type's fields RESOURCE Recipes — task-oriented .e2e.yaml patterns and examples SOURCE Both are byte-exact copies of the pinned vouchfx engine commit's own docs

Get started

Install it, register it, run a suite.

No arguments or environment variables to configure — the server locates its own engine pin and vendored documentation relative to wherever it is installed.

Install & registration

The dotnet tool install command, the .mcp.json snippet, and what run_suite additionally needs on PATH.

What vouchfx-mcp is

The full picture: what it wraps, its honest prerelease status, secret hygiene, and the engine pin.

Troubleshooting

CLI pin mismatches, Docker unavailability, timeouts and cancellation, and where explain_run fits in.

Honest status

Not a black box. A typed result for every call.

6/6 tools real, not stubs — every one exercises the actual vouchfx schema, CLI, or vendored docs

4 taxonomy verdicts kept distinct everywhere — pass / fail / environment error / inconclusive, never conflated

1 engine version this build is pinned to in ENGINE_PIN — a mismatch is always reported, never silently ignored

Install it. Register it. Let your agent run a suite.

Six tools, two vendored documentation resources, one taxonomy-faithful verdict every time.

Install & register Browse the docs