Summary
Turn last night's Allure run into something an assistant can reason about.
The report is already on disk when CI finishes; this reads it back as structured suites and statuses, so failure patterns can be grouped, summarised and explained without anyone scrolling through the generated HTML.
What it is
A single-tool server that reads an Allure HTML report off disk and returns it as formatted JSON: test suites with their names, titles, descriptions, status and start and stop timestamps, in a shape a model can work through.
What you get
- An Allure report read from the directory path you pass as report_dir (get_allure_report)
- The run returned as JSON: suites, titles, descriptions, pass and fail status, start and stop timestamps
- A local stdio server run under uv, reading reports already on the machine
Requirements
Uv and the mcp[cli] package, plus the path to a generated Allure report on the same machine. It reads a report directory; it does not run your tests.
Setup effort
One command — uvx server