TestAtlas — a queryable static map of your Reqnroll suite (with an MCP server for AI agents)

[Karzone]

I built an open-source .NET tool that reads a Reqnroll/SpecFlow solution and writes a single SQLite file capturing the whole shape of the suite — features, scenarios, steps, and their step-definition bindings (bound / unbound / ambiguous), plus page objects, API clients, helpers, and the call/usage edges between them.

It's a syntax-only pass: no build, no compilation, no network, no AI. A solution whose packages have never been restored still maps cleanly, and the same input always produces the same map. Gherkin comes straight from the .feature files; bindings come from the [Given]/[When]/[Then] attributes.

Once the map exists you can ask it things like "does a step for this already exist?" (FTS5 search) or "what scenarios break if I change this class/endpoint?" (impact). There's also an HTML report and a project dependency graph.

The part I'm most interested in feedback on: it ships an MCP server, so an AI coding agent (Claude, Copilot agent mode) can query the map instead of guessing — which cuts down the "agent duplicates a step that already exists" problem that Reqnroll suites are especially prone to.

MIT-licensed, on NuGet as TestAtlas.Cli and TestAtlas.Mcp. Repo (with a sample 8-project shop suite to try it on): https://github.com/Karzone/TestAtlas

Would love feedback from folks running larger Reqnroll suites — especially on the binding-resolution accuracy.