MCP Test Failure Analysis Server
MCP 服务器演示
本项目包含用于 QA 导向的测试失败分析的 Python MCP 服务器,基于 FastMCP 构建。
当前结构
mcp-server-demo/
├── FailureAnalysisFromLogs.py
├── README.md
├── logs/
├── pyproject.toml
├── testFailureAnalysis.py
└── uv.lockRelated MCP server: mcp-log-analyzer
本项目包含内容
testFailureAnalysis.pyanalyze_test_failurecluster_failuresdetect_flaky_tests
FailureAnalysisFromLogs.pyanalyze_test_failure读取并分类
logs/文件夹中的本地.log文件
logs/基于日志的 MCP 服务器使用的示例失败日志
pyproject.tomlPython 版本和依赖配置
uv.lock用于可重复安装的锁定依赖版本
.vscode/mcp.jsontest-failure-analysis、test-failure-analysis-from-logs和mcp-atlassian的 MCP 服务器条目
先决条件
Python
3.11或更高版本uv首次安装依赖时需要互联网访问
安装
从仓库根目录执行:
cd mcp-server-demo
uv sync运行服务器
启动基于输入的 MCP 服务器:
uv run python testFailureAnalysis.py启动基于日志的 MCP 服务器:
uv run python FailureAnalysisFromLogs.py可用工具
analyze_test_failure
使用测试名称、堆栈跟踪和日志分析失败的测试,然后返回可能的失败类别和建议。
FailureAnalysisFromLogs.py 中的 analyze_test_failure
分析 logs/ 文件夹中的本地 .log 文件,并返回失败分类、可能的根本原因、建议以及重要的错误行。它可以分析所有日志、特定的测试名称或确切的日志文件名。
cluster_failures
按堆栈跟踪签名对相似的失败进行分组,以便更容易发现重复的模式。
detect_flaky_tests
审查历史通过/失败结果,并识别表现出不稳定行为的测试。
可选的本地 MCP 配置
仓库根目录包含 .vscode/mcp.json,可供支持 MCP 的工具在开发期间进行本地服务器设置。它包含 test-failure-analysis、test-failure-analysis-from-logs 和 mcp-atlassian 的条目。
Atlassian MCP
本地 MCP 配置包含一个用于 Jira 访问的 mcp-atlassian 服务器条目。
如何使用
在支持 MCP 的客户端中使用 .vscode/mcp.json 中配置的 mcp-atlassian 条目。
若要手动运行,请使用:
JIRA_URL=<your-jira-url> \
JIRA_USERNAME=<your-jira-username> \
JIRA_API_TOKEN=<your-jira-api-token> \
uvx mcp-atlassian故障排除
如果
uv不可用,请安装它并重新打开终端。如果依赖安装失败,请确认 Python
3.11+处于活动状态。如果服务器无法启动,请在
mcp-server-demo中再次运行uv sync。
工作流程图片位于 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
- FlicenseNot gradedqualityDmaintenanceEnables 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.
- AlicenseNot gradedqualityDmaintenanceAnalyzes log files locally using Ollama and files structured GitHub Issues automatically, with all processing kept on your machine.1MIT
- AlicenseAqualityAmaintenanceProvides tools to analyze and debug GitHub Actions CI failures, including summarizing failures, detecting flaky tests, and suggesting fixes.10161ISC
- FlicenseNot gradedqualityDmaintenanceProvides tools to analyze and compare JVM thread dumps, summarizing thread states and detecting deadlocks.
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.
Synthesize GitHub Issues, HN and App Store reviews into ranked pain clusters. Pay-per-call x402.
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