TestAtlas MCP server

<!-- mcp-name: io.github.Karzone/TestAtlas.Mcp --> &nbsp;TestAtlas

A queryable, semantic map of your .NET test-automation solution — in one SQLite file, served to your AI agent over MCP.

Zero config&nbsp; ·&nbsp; No AI&nbsp; ·&nbsp; No network&nbsp; ·&nbsp; Deterministic

11 MCP tools resolvestep · stepcatalog · impact · searchsteps · searchscenarios · getscenario · getstepdefinition · listtags · listendpoints · projectdependencies · stats

The problem · See it in action · Quick start · MCP · Commands · Fresh maps · Roadmap

The problem

Large test-automation solutions are hard to navigate — for humans and for AI agents. Asked to automate a new story, an agent can't see which steps already exist, where similar code lives, or what conventions the solution follows — so it duplicates steps and misplaces code. TestAtlas indexes the solution once into a single SQLite map and answers those questions precisely: deterministically, offline, without a model or a network call.

See it in action

Index the bundled 8-project sample once — testatlas index samples/SampleShop/SampleShop.sln — then ask it questions from the terminal. Every number below is real output from that run:

$ testatlas stats sampleshop.db
TestAtlas map: sampleshop.db (schema v5)

totals: 8 project(s), 15 class(es), 36 method(s), 14 step definition(s)
class kinds:
  api_client     7
  page_object    4
  step_class     4

gherkin: 4 feature(s), 5 scenario(s), 16 step(s)
bound steps: 16 · unbound: 0 · ambiguous: 0
endpoints: 3 (3 call site(s))

…or let your agent ask them over MCP. Here an agent checks whether a step it is about to write already exists — resolve_step answers with the definitions that would bind it, or the closest near-misses to reuse instead:

Shortened. The full README is on GitHub.