TestAtlas MCP server

TestAtlas reads your .NET test project once and writes a small map file. That map holds every feature, scenario, step and helper class in your test suite. It is handy if you work with Reqnroll or SpecFlow tests and want your AI to reuse what already exists instead of inventing new steps.

What this MCP server does

You first run a command that scans your test project and writes a map file. Then you connect this helper to your AI and point it at that map file. When you ask something like whether a step already exists, your AI sends the question to the helper. The helper reads the map file and sends back the exact steps, scenarios or classes that match. You see the answer right in your chat, with file names and line numbers.

Click to zoom

What you can do with it

• Check whether a step you are about to write already exists
• See which scenarios would break if you change a class or method
• Search your step definitions and scenarios by keyword
• List all tags used in your test suite with counts
• List the HTTP endpoints your tests call
• See which projects depend on which other projects
• Get a summary of how many projects, classes and steps you have

Try asking your AI

• “Does a step for adding a product to the cart already exist?”
• “What scenarios would be affected if I change the ProductsApiClient class?”
• “Show me the full detail of the scenario called User logs in successfully”
• “Which projects depend on the Core project?”

What it gives back to you

You get short, structured answers in the chat. For a step question, you get the exact step text, its keyword, and the file and line where it lives, or a list of close matches if nothing fits. For an impact question, you get the list of scenarios that would be affected. For a summary question, you get counts of projects, classes, methods and steps.

Before you start

Who it's for

Test automation engineers and developers who work on .NET Reqnroll or SpecFlow test suites and want their AI to stop duplicating steps.