Quality Transformation Coach Assistent MCP server
This server is an MCP-based assistant for software quality transformation, offering 16 tools for code analysis, issue/defect analysis, CI/CD insights, AI readiness, and knowledge/maturity assessments.
Code Analysis:
analyze_code_quality,analyze_test_coverage,detect_test_patterns,analyze_flaky_tests— scan repositories for metrics, coverage, patterns, and flaky tests.Issue & Defect Analysis:
defect_trend_analysis,quality_hotspot_detection,root_cause_categories— analyze issue trends, hotspots, and root causes.CI/CD:
pipeline_health,test_result_summary,cicd_readiness_scan,quality_gate_check— assess pipeline health, summarize test results, run readiness scans, and check quality gates.AI Readiness:
ai_readiness_scan— run a 60-question AI maturity assessment.Knowledge & Maturity:
maturity_assessment,quality_recommendations,framework_lookup,generate_quality_report— perform TMMi/ISO 25010 assessments, get improvement advice, look up framework details, and generate Markdown reports.Integration: Works via OpenCode chat (MCP tools) or direct Python API, with a config-driven setup supporting GitHub, CI/CD, and local repositories.
Provides tools for analyzing GitHub repositories, issues, pull requests, and GitHub Actions CI/CD pipelines to assess code quality, test coverage, defect trends, and quality gates.
Quality Transformation Coach MCP Server
Een MCP-server die als assistent dient voor software quality transformation — bedoeld voor zowel de quality transformation coach (overzicht, advisering, maturity assessments) als het development/test team (hands-on kwaliteitsanalyse, testondersteuning, CI/CD-inzichten).
Functionaliteiten
De server biedt 16 tools verdeeld over 5 categorieën:
Code Analyse
Tool | Beschrijving |
| Scan een repo voor code kwaliteits-metrieken (complexity, duplication, smells) |
| Analyseer test coverage en identificeer gaps |
| Herken test patterns (unit/integration/e2e) en anti-patterns |
| Detecteer flaky tests op basis van CI-logs |
Issue & Defect Analyse
Tool | Beschrijving |
| Analyseer issue-trends (aanwas, resolutietijd, severity) |
| Identificeer modules met hoogste defect-dichtheid |
| Categoriseer bugs per oorzaak (code, design, requirements, security) |
CI/CD
Tool | Beschrijving |
| Analyseer CI/CD pipeline gezondheid (success rate, doorlooptijd) |
| Agregeer test results vanuit CI runs |
| Voer een CI/CD Readiness Scan uit (102 vragen, 5 domeinen) |
| Controleer of kwaliteits gates behaald zijn |
AI Readiness
Tool | Beschrijving |
| Voer een AI Readiness Scan uit (60 vragen, 5 AI-domeinen) |
Kennis & Maturity
Tool | Beschrijving |
| Voer een TMMi/ISO 25010 maturity scan uit |
| Geef context-gevoelige verbeteradviezen |
| Raadpleeg kennisbank voor kwaliteitsmodellen |
| Genereer een compleet kwaliteitsrapport in Markdown |
Related MCP server: MCP Test Failure Analysis Server
Installatie
Vereisten
Python 3.11+
GitHub Personal Access Token (voor issue/PR data)
Lokale installatie
git clone git@github.com:Cerios-TechLab/quality-transformation-coach-assistent.git
cd quality-transformation-coach-assistent
python3.11 -m venv .venv
source .venv/bin/activate
pip install -e ".[dev]"Configuratie
Kopieer config.example.yaml naar config.yaml en pas aan:
github:
token_env: GITHUB_TOKEN
default_org: "Cerios-TechLab"
cicd:
provider: github_actions
coverage:
source: local
format: cobertura
projects:
- name: "cerios-clinic"
repo: "/srv/cerios-clinic"
github: "Steavy/cerios-clinic"OpenCode integratie
Voeg toe aan ~/.config/opencode/opencode.json onder mcp:
"quality-coach": {
"type": "local",
"command": [
"/opt/quality-coach-mcp/.venv/bin/python",
"-m",
"quality_coach_mcp.server"
],
"cwd": "/opt/quality-coach-mcp",
"enabled": true
}Herstart OpenCode na wijzigingen:
systemctl restart opencode-serve-4096Gebruik
Via OpenCode chat
De tools zijn beschikbaar als MCP-tools in elke OpenCode-sessie. Voorbeelden:
"Wat is de test coverage van
/srv/cerios-clinic?""Geef een maturity assessment voor project X met scores
{'test_planning': 3, 'test_design': 2}""Genereer een quality report voor gateway met een periode van 30 dagen"
"Wat zegt ISO 25010 over Maintainability?"
"Check de quality gate pull_request voor Steavy/cerios-clinic"
Directe Python API
from quality_coach_mcp.tools.code_analysis import CodeAnalysisTools
from quality_coach_mcp.config import load_config
config = load_config()
tools = CodeAnalysisTools(config)
import asyncio
result = asyncio.run(tools.analyze_code_quality("/srv/cerios-clinic"))
print(result)Kennisbank
De server bevat een embedded kennisbank met:
ISO 25010 — 8 kwaliteitskenmerken met sub-characteristics
TMMi — 5 maturity levels met assessment areas
Test Patterns — Herkenbare patronen en anti-patterns
Quality Gates — Standaard criteria voor PR, release, sprint
Recommendations — Context-gevoelige verbeteradviezen
CI/CD Readiness — Maturitychecklist voor CI/CD-processen (102 vragen)
AI Readiness — Maturitychecklist voor AI-toepassing (60 vragen, 5 domeinen)
Kennisbank-bestanden staan in src/quality_coach_mcp/knowledge/ als YAML.
Development
Tests draaien
pip install -e ".[dev]"
pytest tests/ -vProjectstructuur
src/quality_coach_mcp/
├── server.py # FastMCP server entry point (16 tools)
├── config.py # Config loading
├── models/types.py # Pydantic data models
├── tools/
│ ├── code_analysis.py # Code kwaliteitsanalyse
│ ├── issue_analysis.py # Issue & defect analyse
│ ├── cicd_tools.py # CI/CD pipeline tools
│ └── knowledge_tools.py # Kennis & maturity tools
├── adapters/
│ ├── github_adapter.py # GitHub API wrapper
│ └── cicd_adapter.py # CI/CD resultaten parser
└── knowledge/
├── iso25010.yaml
├── tmmi.yaml
├── test_patterns.yaml
├── quality_gates.yaml
├── recommendations.yaml
├── cicd_readiness.yaml
└── ai_readiness.yamlLicentie
Onderdeel van Cerios TechLab.
Available Tools
16 toolsai_readiness_scanAi Readiness ScanB
Run an AI Readiness Scan assessment with 60 questions across 5 AI domains.
Inputs: project (required), answers. Returns: object
analyze_code_qualityAnalyze Code QualityB
Scan a repository for code quality metrics (complexity, duplication, smells).
Inputs: repo_path (required), branch. Returns: object
analyze_flaky_testsAnalyze Flaky TestsC
Detect flaky tests from CI run data.
Inputs: github_ref (required), run_ids. Returns: object
analyze_test_coverageAnalyze Test CoverageB
Analyze test coverage by comparing test files against source files.
Inputs: repo_path (required). Returns: object
cicd_readiness_scanCicd Readiness ScanB
Run a CI/CD Readiness Scan assessment with 102 questions across 5 domains.
Inputs: project (required), answers. Returns: object
defect_trend_analysisDefect Trend AnalysisB
Analyze issue trends (volume, resolution time, severity) for a repository.
Inputs: github_ref (required), days. Returns: object
detect_test_patternsDetect Test PatternsC
Detect test patterns and anti-patterns in a repository.
Inputs: repo_path (required). Returns: object
framework_lookupFramework LookupA
Look up information about a quality framework (ISO 25010, TMMi).
Inputs: framework (required), topic. Returns: object
generate_quality_reportGenerate Quality ReportC
Generate a comprehensive Markdown quality report.
Inputs: project (required), period, coverage_pct, maturity_scores, +1 more. Returns: result
maturity_assessmentMaturity AssessmentC
Run a TMMi maturity assessment for a project.
Inputs: project (required), scores. Returns: object
pipeline_healthPipeline HealthA
Analyze CI/CD pipeline health (success rate, duration trends).
Inputs: github_ref (required), days. Returns: object
quality_gate_checkQuality Gate CheckC
Check if quality gates are met for a project.
Inputs: github_ref (required), gate_id, metrics. Returns: object
quality_hotspot_detectionQuality Hotspot DetectionB
Identify files with the highest defect density (hotspots).
Inputs: github_ref (required). Returns: object
quality_recommendationsQuality RecommendationsC
Generate prioritised quality improvement recommendations.
Inputs: maturity_scores (required), context. Returns: object
root_cause_categoriesRoot Cause CategoriesB
Categorise closed bugs by root cause (code, design, requirements, security).
Inputs: github_ref (required). Returns: object
test_result_summaryTest Result SummaryA
Get test results summary for a specific CI workflow run.
Inputs: run_id (required), github_ref (required). Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 16 tools
Each tool targets a distinct aspect of quality (pipeline health, test results, code quality, readiness scans, defects), and the descriptions help differentiate them. There is mild overlap between analysis tools like analyze_code_quality and quality_hotspot_detection, but their scopes are clear enough to avoid major misselection.
All names are snake_case and descriptive, making the set readable. However, the convention is mixed: some tools use noun phrases (pipeline_health, framework_lookup) while others use verb-led names (analyze_code_quality, detect_test_patterns, generate_quality_report), so the naming pattern is not fully consistent.
At 16 tools, the set is slightly over the ideal 3-15 range but still reasonable given the broad quality transformation domain. Each tool earns its place by covering a distinct part of the assessment, analysis, and reporting workflow.
The tool surface covers assessment, analysis, recommendations, and report generation across code quality, testing, CI/CD, and maturity frameworks. A minor gap is the lack of operational follow-up tools such as tracking remediation progress, but the core workflow is well covered.
Maintenance
Related MCP Connectors
Security scanning for code, containers and IaC: request scans, read findings, report fixes.
Track QA and verification: test runs, reviews, issues, system docs, flows and PRs.
30+ deterministic dev and delivery tools: linting, metrics, diagrams, model advice, AI-text checks.
Triage failing GitHub Actions jobs and see what self-heal repaired, in natural language.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceAutomates Java Maven testing workflows with decision table-based test generation, security vulnerability scanning, JaCoCo coverage analysis, and Git automation.-
- FlicenseBqualityDmaintenanceProvides tools to analyze test failures, cluster similar failures, and detect flaky tests from input or log files, helping QA teams debug and triage issues.3-
- AlicenseAqualityCmaintenanceProvides tools to analyze and debug GitHub Actions CI failures, including summarizing failures, detecting flaky tests, and suggesting fixes.104 npm1ISC
- AlicenseCqualityCmaintenanceAutomates generation of QA artifacts such as API tests, E2E tests, and documentation exports. It supports REST Assured, Cypress, and Excel/Word document generation.59 npmMIT