MCP Test Failure Analysis Server
Allows to manage Jira issues for tracking test failures and bugs.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP Test Failure Analysis ServerAnalyze test failure: login page timeout"
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.
MCP Server Demo
This project contains Python MCP servers for QA-oriented test failure analysis, built with FastMCP.
Current Structure
mcp-server-demo/
├── FailureAnalysisFromLogs.py
├── README.md
├── logs/
├── pyproject.toml
├── testFailureAnalysis.py
└── uv.lockRelated MCP server: Regression-JIRA Integration System
What This Project Includes
testFailureAnalysis.pyanalyze_test_failurecluster_failuresdetect_flaky_tests
FailureAnalysisFromLogs.pyanalyze_test_failureReads and classifies local
.logfiles from thelogs/folder
logs/Sample failure logs used by the log-based MCP server
pyproject.tomlPython version and dependency configuration
uv.lockLocked dependency versions for reproducible installs
.vscode/mcp.jsonMCP server entries for
test-failure-analysis,test-failure-analysis-from-logs, andmcp-atlassian
Prerequisites
Python
3.11or lateruvInternet access for the first dependency install
Installation
From the repository root:
cd mcp-server-demo
uv syncRunning the Server
Start the input-based MCP server with:
uv run python testFailureAnalysis.pyStart the log-based MCP server with:
uv run python FailureAnalysisFromLogs.pyAvailable Tools
analyze_test_failure
Analyzes a failed test using the test name, stack trace, and logs, then returns a likely failure category and recommendation.
analyze_test_failure in FailureAnalysisFromLogs.py
Analyzes local .log files from the logs/ folder and returns failure classification, likely root cause, recommendation, and important error lines. It can analyze all logs, a specific test name, or an exact log file name.
cluster_failures
Groups similar failures by stack trace signature so repeated patterns are easier to spot.
detect_flaky_tests
Reviews historical pass/fail results and identifies tests that show flaky behavior.
Optional Local MCP Configuration
The repository root contains .vscode/mcp.json, which can be used by MCP-aware tooling for local server setup during development. It includes entries for test-failure-analysis, test-failure-analysis-from-logs, and mcp-atlassian.
Atlassian MCP
The local MCP configuration includes an mcp-atlassian server entry for Jira access.
How to use it
Use the configured mcp-atlassian entry from .vscode/mcp.json in your MCP-aware client.
To run it manually, use:
JIRA_URL=<your-jira-url> \
JIRA_USERNAME=<your-jira-username> \
JIRA_API_TOKEN=<your-jira-api-token> \
uvx mcp-atlassianTroubleshooting
If
uvis not available, install it and reopen the terminal.If dependency installation fails, confirm Python
3.11+is active.If the server does not start, run
uv syncagain insidemcp-server-demo.
Work Flow Image in Image folder at image/project-workflow.png
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Flicense-quality-maintenanceA utility that helps diagnose and fix GitHub Actions workflow failures by analyzing run logs, identifying common failure patterns, and suggesting specific fixes through a structured decision tree.Last updated1
- Flicense-qualityDmaintenanceEnables 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.Last updated
- Alicense-qualityDmaintenanceAnalyzes log files locally using Ollama and files structured GitHub Issues automatically, with all processing kept on your machine.Last updated1MIT
- AlicenseAqualityAmaintenanceProvides tools to analyze and debug GitHub Actions CI failures, including summarizing failures, detecting flaky tests, and suggesting fixes.Last updated10251ISC
Related MCP Connectors
Flaky test detection, root cause analysis, and fix suggestions for development teams.
BuildPulse CI test analytics for AI agents — flaky tests, coverage, and CI run history.
Investigate errors, track deployments, analyze performance, and manage application monitoring
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/rudrathkr/MCPServerCreationPythonSDK'
If you have feedback or need assistance with the MCP directory API, please join our Discord server