Keyless local MCP server for QA: standards retrieval, effort estimation, doc review, test analysis.
io.github.gvasile29/qai-consultant-mcp MCP Server
This keyless local MCP server for QA provides capabilities focused on QA support tasks, including standards retrieval, effort estimation, documentation review, and test analysis. The server is identified by the slug io-github-gvasile29-qai-consultant-mcp and is described as operating locally without key-based access.
π οΈ Key Features
Standards retrieval
Effort estimation
Doc review
Test analysis
Keyless local operation
π Use Cases
Retrieve QA standards for reference
Estimate effort for QA activities
Review documentation as part of QA workflows
Analyze tests and test-related information
β‘ Developer Benefits
Local MCP integration for QA tooling
Focused support on common QA tasks: standards, estimation, review, and analysis
β οΈ Limitations
No additional details provided on supported protocols, tools, inputs/outputs, or configuration beyond being keyless and local
An open-source AI agent that acts as a senior QA Architect β automatically generating a Test Strategy, Risk Register, Effort Estimation Report, and Test Plan from a simple project description, plus deterministic QA Document Quality Review and Test Results Analysis for evaluating what already exists. Also available as an MCP server so Claude Code, Claude Desktop, and claude.ai can ground their own QA work in the same standards and numbers.
Streamlit IntroStreamlit MCP announcement in sidebarStreamlit Project Discovery dialogueStreamlit Risk RegisterStreamlit Effort EstimationStreamlit Test StrategyStreamlit Test Plan
# 1. Clone and install
git clone https://github.com/gvasile29/qai-consultant.git
cd qai-consultant
pip install -r requirements.txt
# 2. Set up API keyscp .env.example .env# Edit .env and fill in the 4 keys (see Prerequisites below)# 3. Build the knowledge base (one-time, pushes to Pinecone)
python src/ingest.py
# 4. Run
python src/cli.py # Terminal UI
streamlit run src/app.py # Web UI β http://localhost:8501
Creating a Test Strategy from scratch is time-consuming and requires deep QA expertise. Most teams either skip it, do it superficially, or spend days researching methodologies.
QAI Consultant eliminates this bottleneck by combining established QA methodologies, industry standards (ISTQB, OWASP, ISO 26262, A-SPICE), and expert knowledge into an AI agent that thinks like a seasoned QA Architect.
Who Is This For?
QA Engineers who need structured guidance on test strategy
Engineering Managers who need effort estimations and resource planning
Development teams without a dedicated QA Architect
QA Consultants who want to accelerate their delivery
What QAI Consultant Generates
From a single 11-question dialogue, QAI Consultant automatically generates four documents:
Document
What it contains
β οΈ Risk Register
Risk matrix, likelihood/impact analysis, mitigations per risk
π Effort Estimation Report
PERT-based breakdown, team capacity analysis, confidence score
π Test Strategy
ISTQB-aligned strategy tailored to your stack, methodology, and compliance
π Test Plan
IEEE 829-aligned plan with entry/exit criteria, schedule, and AI tool oversight
All outputs are saved as Markdown files and available for PDF download.
Knowledge Base
QAI Consultant's recommendations are grounded in real QA standards and methodologies:
Name of your Pinecone index (e.g. qai-consultant, dimensions: 384, metric: cosine)
bash
cp .env.example .env# Edit .env and fill in all four values
Architecture
QAI Consultant Architecture
How It Works
code
You describe your project (11 questions)
β
QAI retrieves relevant knowledge from Pinecone (parallel RAG, 3 threads)
β
QAI analyzes risks from your context β Risk Register (Mistral API)
β
QAI estimates effort using PERT + industry benchmarks β Effort Report
β
QAI generates a Test Strategy backed by QA standards β Test Strategy (Mistral API)
β
QAI generates an IEEE 829-aligned Test Plan β Test Plan (Mistral API)
β
Four documents ready for Markdown + PDF download
LLM calls use Mistral API as the primary provider, with OpenRouter as automatic fallback.
MCP Server (for Claude Code, Claude Desktop, claude.ai)
QAI Consultant is also available as a local, fully keyless MCP server β
qai-consultant-mcp. No Pinecone, no Mistral/OpenRouter API keys: it runs a
local embedding index over the same knowledge base and exposes deterministic
QA effort estimation, so your own AI coding assistant can ground its QA
planning directly, no separate LLM call needed.
qai-consultant-mcp answering a retrieve_qa_knowledge call in MCP Inspector
bash
uvx qai-consultant-mcp
Claude Code:
bash
claude mcp add qai-consultant -- uvx qai-consultant-mcp
Grounding chunks from the KB (ISTQB, OWASP, IEEE, ISO, EU AI Act), filterable by category
list_kb_sources
Every document in the KB, grouped by category
estimate_qa_effort
Deterministic PERT-based effort estimate (no LLM narrative β you write your own from the numbers)
review_qa_document
Deterministic 0β100 quality score for an existing Test Plan/Strategy/test case list across six ISTQB/IEEE-829 dimensions, with findings + KB citations
analyze_test_results
Deterministic health metrics from JUnit XML/CSV test execution data β flaky tests, ever-failing tests, slowest tests, failure clustering
Prompts:qa_project_interview (the same 11-question intake this app uses), risk_register_structure, test_strategy_structure, test_plan_structure β each grounds the client's generation in retrieve_qa_knowledge with [Source N] citations.
Privacy: usage telemetry is off by default. Set QAI_TELEMETRY=1 to opt in; even then, only tool name/success/duration/category and an anonymous install ID are sent β never your query text or project details.
Feedback Loop
After each generation, QAI asks: "Was this strategy useful?"
Yes β strategy saved to knowledge_base/generated_strategies/ and included in the next re-ingestion
Partially β strategy saved with your improvement notes
No β discarded
This creates a feedback loop where QAI learns from validated real-world outputs over time.
Roadmap
v0.1 β Core agent + CLI + Streamlit Web UI
v0.2 β Feedback loop β validated strategies grow the knowledge base
v2.5.1 β Knowledge base β new evaluation_audit/ pillar: process/test maturity models, audit methodology, security/compliance audit, real public failure case studies
v2.5.2 β EU AI Act Article 50 transparency patch β sidebar AI-interaction notice + visible "AI-generated content" label on every generated document
v2.6.0 β EU AI Act knowledge base pillar β risk tiers, provider/deployer obligations, Article 50 transparency, Articles 9-15 testing implications, conformity assessment, timeline
v3.0.0 β MCP server MVP β local, keyless qai-consultant-mcp (standards-grounded retrieval + deterministic effort estimation), in-app announcement, and machine-readable AI-generated marking (EU AI Act Article 50(2))
v3.1.0 β Evaluation Package β QA Document Quality Review (deterministic ISTQB/IEEE-829 rubric scoring an existing Test Plan/Strategy/test case list, with an optional AI narrative) and Test Results Analysis (flaky/ever-failing/slowest/failure-clustering metrics from JUnit XML/CSV, grounding the Risk Register in real execution data); available in the web app, CLI (--review, --results), and the MCP server (review_qa_document, analyze_test_results)
v3.1.1 β Visit counter β a running total of app visits now shows in the sidebar, persisted in Pinecone so it survives redeploys
v3.1.2 β Fix β the 3.1.1 visit counter never actually incremented (Pinecone rejected its all-zero placeholder vector); now works correctly
v3.1.3 β Fix β the visit counter's label was in Romanian ("vizite") instead of English; now reads "visits" to match the rest of the app's UI copy
v3.1.4 β Added the mcp-name marker to README_MCP.md (PyPI long description) β a prerequisite for listing qai-consultant-mcp in the official Anthropic MCP registry; no functional change
v3.2 Remote MCP + distribution β hosted server connectable from claude.ai, registry submissions
Contributing
QAI Consultant is built by the QA community, for the QA community.
Contributions are welcome:
π Add new knowledge sources to knowledge_base/
π§ Share expert knowledge using the prompts in knowledge_base/expert_knowledge/
π Report bugs or suggest features via GitHub Issues