QAForge MCP
The world's first all-in-one QA engineering MCP server — 12 QA tools for Claude Code, in one place.
Generate test cases, run security scans, detect flaky tests, diff browsers, check accessibility, baseline performance, and more — all from natural language, inside Claude.
Tools
| # | Tool | What it does |
|---|---|---|
| 1 | generate_test_cases |
FRD/Swagger → numbered test cases with priority + coverage gaps |
| 2 | detect_flaky_tests |
Statistical flaky-test detection across JUnit XML runs, AI root-cause |
| 3 | generate_security_tests |
OWASP Top 10 Postman collection + k6 security script |
| 4 | narrate_report |
JUnit/Allure report → stakeholder-ready narrative, optional Slack post |
| 5 | diff_browsers |
Cross-browser (Chrome/Firefox/WebKit) diffing via Playwright |
| 6 | ai_test_executor |
Executes structured test cases against a live URL |
| 7 | bug_report_generator |
AI bug report + optional Jira ticket creation |
| 8 | regression_impact_analyzer |
git diff → impacted test areas + risk levels |
| 9 | accessibility_checker |
WCAG 2.1 audit via axe-core, AI fix suggestions |
| 10 | performance_baseline_mcp |
k6 load test, P50–P99, baseline regression alerts |
| 11 | environment_health_checker |
Pre-test service health checks, Slack alerts |
| 12 | test_data_generator |
Faker-based test data + edge cases + blockchain fields |
Install
pip install qaforge-mcp
playwright install chromium firefox webkit # needed for browser/accessibility tools
Optionally install k6 for the performance tools.
Register with Claude Code
claude mcp add --scope user qaforge -e ANTHROPIC_API_KEY=your-key-here -- python -m qaforge_mcp
This makes all 12 tools available in every Claude Code session on your machine.
Optional integrations
Add any of these to the same -e flags (or a .env file next to your working directory) to unlock more:
| Variable | Enables |
|---|---|
ANTHROPIC_API_KEY |
AI-powered analysis (test generation, root-cause classification, bug reports) |
JIRA_URL, JIRA_EMAIL, JIRA_TOKEN, JIRA_PROJECT_KEY |
Auto-create Jira tickets from bug_report_generator |
SLACK_WEBHOOK |
Post test reports and environment alerts to Slack |
Tools work without any of these configured — AI-dependent tools fall back to non-AI output, and Jira/Slack features simply no-op.
Requirements
- Python 3.11+
- Playwright browsers for
diff_browsers,accessibility_checker,ai_test_executor - k6 for
performance_baseline_mcpand the security k6 script
License
MIT
1 maintainer
Metadata
1 maintainer
Release files for qaforge-mcp 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| qaforge_mcp-1.0.0.tar.gz | 30.4 kB | Without provenance | Details for qaforge_mcp-1.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| qaforge_mcp-1.0.0-py3-none-any.whl | Python 3 | none | any | Details for qaforge_mcp-1.0.0-py3-none-any.whl |
Total release size: 67.9 kB
Release files / qaforge_mcp-1.0.0.tar.gz
| Download URL | qaforge_mcp-1.0.0.tar.gz |
|---|---|
| Size | 30.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f66cd9c0714f7363219ea2165835ec5d44cf65aecffadab2c4c4f69b161eaf77
|
|
BLAKE2b-256 checksum How to use checksums |
009cbf771f16821f1057f75fefb7848dd266f71de9ba74ae80402f2f4751eacc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.10
|
Release files / qaforge_mcp-1.0.0-py3-none-any.whl
| Download URL | qaforge_mcp-1.0.0-py3-none-any.whl |
|---|---|
| Size | 37.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a74ac36a339eb4c55557d6fe1342b10900bd6baaa195844930633963aebe6dd1
|
|
BLAKE2b-256 checksum How to use checksums |
8aa6b5cf3a38edf9a17ffef40aefa3c18aaa5277827c51ad2d9ee0796cd785c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.10
|
Security for qaforge-mcp 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
