How do I use allure-mcp-analyzer?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@allure-mcp-analyzer Analyze the failures in allure-results and tell me which root causes block the release." That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

allure-mcp-analyzer

by gurevich89

Overview Schema Source Related Servers Score Discussions Admin

Python

Local

🔍 Allure MCP Analyzer — AI-driven root-cause analysis for test failures

An MCP server + CLI that reads Allure results, clusters failures by normalized error signature (deterministic, no LLM), and then asks an LLM to explain each cluster — product bug, test bug, infrastructure, flaky, or data.

This is the pattern I use to turn a 300-red-test CI run into "3 root causes, here is what to do" in seconds. The clustering step is what makes it cheap and reliable: the LLM analyzes a handful of clusters, not every test.

✨ What's inside

Area	Highlights
Parsing	Reads `allure-results/*-result.json` (status, message, trace, labels, timings)
Clustering	Normalizes volatile tokens (ids, hex, timestamps, paths, numbers) → stable signature → clusters sorted by impact
Root-cause analysis	One LLM call per cluster; strict JSON contract (`category`, `summary`, `confidence`, `evidence`, `suggested_action`) with defensive parsing
Pluggable LLM	`FakeLLM` (offline, deterministic — used in tests & CI without a key) or `AnthropicLLM` (lazy import)
MCP server	Tools: `load_results`, `list_failures`, `cluster_failures`, `analyze_cluster`, `analyze_run`
CLI	`allure-analyze ./allure-results --md report.md --json report.json --top 5` — exit code 1 when failures exist
Reports	Markdown (PR comment / Slack) with a summary table + collapsible affected-tests lists; JSON for dashboards
Agent Skills	`.claude/skills/allure-triage` — a Claude Code playbook that runs the whole triage flow
CI	Lint + tests on 3.11/3.12, demo report uploaded as an artifact

Related MCP server: Regression-JIRA Integration System

📁 Layout

src/allure_mcp_analyzer/
├── parser.py     # Allure results → TestResult
├── cluster.py    # signature normalization + clustering
├── rca.py        # prompt, LLM call, JSON contract → RootCause
├── report.py     # Markdown / JSON rendering
├── llm.py        # LLM protocol, FakeLLM, AnthropicLLM
├── server.py     # FastMCP server (5 tools)
└── cli.py
examples/allure-results/   # 9 sample results → 3 clusters (assertion, timeout, locator)
tests/                     # unittest / pytest
.claude/skills/            # agent skill for CI triage
.mcp.json                  # register the server with Claude Code / Cursor

🚀 Quick start

pip install -e ".[dev]"            # core + tests
pytest -q                          # 17 tests, all offline

# CLI on the bundled example (FakeLLM when no API key is set)
allure-analyze examples/allure-results --top 3

Real analysis:

pip install -e ".[llm,mcp]"
export ANTHROPIC_API_KEY=...        # see .env.example
export ANTHROPIC_MODEL=...          # https://docs.claude.com/en/docs/about-claude/models
allure-analyze ./allure-results --md report.md

🤖 As an MCP server (Claude Code / Cursor)

.mcp.json is already in the repo — from the repo root:

claude
> Use allure-analyzer to triage ./allure-results and tell me which clusters block the release.

Or invoke the bundled skill directly: /allure-triage.

🧠 How clustering works

"AssertionError: expected total 59.98 but got 49.99"
"AssertionError: expected total 120.00 but got 100.00"
        ↓ normalize()
"AssertionError: expected total <n> but got <n>"     → one cluster, 3 tests

Timeouts on a shared dependency collapse the same way, so an outage shows up as one infrastructure cluster instead of fifty unrelated reds.

🔌 CI integration

The workflow uploads report.md / report.json as an artifact on every run. To post the Markdown as a PR comment, pipe it through gh pr comment --body-file report.md.

📄 License

MIT

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

No tool schema history has been recorded yet.

This server cannot be installed

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Maintenance

ActivityMaintained

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

TestMu AI (formerly LambdaTest)OAuth
io.github.LambdaTest
Agentic testing: HyperExecute jobs, test failure triage, SmartUI visual diffs, a11y audits
Testing & QA Tools CI/CD & DevOps Browser Automation
1
buildpulse-mcp
io.github.BuildPulseLLC
BuildPulse CI test analytics for AI agents — flaky tests, coverage, and CI run history.
CI/CD & DevOps Testing & QA Tools
2
Cypress Cloud MCP BOAuth
io.cypress.mcp
Direct access to Cypress tests results and accessibility reports in your AI workflow.
Testing & QA Tools CI/CD & DevOps
24
Trunk Flaky TestsOAuth
io.trunk
Flaky test detection, root cause analysis, and fix suggestions for development teams.
CI/CD & DevOps Testing & QA Tools Autonomous Agents
2

Related MCP Servers

MCP-Allure
Testing & QA Tools Developer Tools Code Analysis
crisschan
A
license
C
quality
D
maintenance
A server that converts Allure test reports into LLM-friendly formats, enabling AI models to better analyze test results and provide insights about test failures and potential fixes.
Updated 10 months ago (2025-10-27 01:07 UTC)
1
11
Apache 2.0
Regression-JIRA Integration
Testing & QA Tools Project Management Databases
nanyang12138
F
license
Not graded
quality
D
maintenance
Enables intelligent analysis of regression test failures and automatic discovery of solutions in JIRA. Analyzes test logs using AI-driven algorithms and matches errors with relevant JIRA issues through natural language interactions.
Updated 10 months ago (2025-11-04 06:28 UTC)
-
MCP Test Failure Analysis
Testing & QA Tools Developer Tools
rudrathkr
F
license
B
quality
D
maintenance
Provides tools to analyze test failures, cluster similar failures, and detect flaky tests from input or log files, helping QA teams debug and triage issues.
Updated 4 months ago (2026-04-26 12:59 UTC)
3
-
TestPilot MCP
Testing & QA Tools Developer Tools
Kirit2121
A
license
Not graded
quality
D
maintenance
Enables AI models (Claude, ChatGPT, GitHub Copilot) to run and analyze local tests, rerun failures, and orchestrate QA workflows using existing UI and API test frameworks.
Updated 9 months ago (2025-12-18 13:08 UTC)
21
MIT

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gurevich89/allure-mcp-analyzer'

If you have feedback or need assistance with the MCP directory API, please join our Discord server