qa-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | Your API key for the QA MCP server |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_stage_configC | Get configuration and recommendations for a specific stage |
| get_recommended_promptC | Get the recommended prompt structure for a specific stage |
| get_model_recommendationC | Get recommended model (Sonnet for analysis, Haiku for execution) |
| create_session_checkpointC | Save a clean output at the end of each stage for next stage input |
| load_stage_checkpointC | Load clean output from previous stage (not full chat) |
| validate_context_healthC | Check if context is clean and not bloated |
| create_handoff_summaryC | Create clean handoff to start new session |
| save_test_casesC | Save test cases for future reuse on bug fixes/regressions |
| find_reusable_test_casesD | Find existing test cases for reuse |
| validate_execution_readinessC | Check if test cases are ready for execution |
| validate_qa_outputD | Validate output before moving to next stage |
| create_test_caseC | Create a new test case with title, description, steps, and expected result |
| record_test_resultC | Record the result of a test execution |
| report_defectC | Report a new defect/bug found during testing |
| generate_qa_reportB | Generate comprehensive QA report with all metrics and statistics |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Each tool targets a distinct aspect of QA workflow (handoff, checkpoints, test cases, reporting, recommendations, validations). No two tools appear to do the same thing.
All tools follow a consistent verb_noun snake_case pattern (e.g., create_test_case, validate_context_health), making it easy to predict functionality.
15 tools is well-scoped for a QA server covering test creation, execution, reporting, defect tracking, and stage management. Each tool serves a clear purpose.
Core workflows (create, find, execute, report, validate) are covered. Minor gaps include missing update/delete operations for test cases, but the surface is sufficient for the intended structured process.