qa-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| autoCompleteRfCuC | Completa RF/CU/pasos en rf-cu.md según formato requerido. |
| generateRestTestsC | Genera tests API Rest Assured en la ruta configurada. |
| generateE2ETestsC | Genera tests E2E Cypress en la ruta configurada. |
| exportETPAsExcelC | Exporta el ETP a Excel usando exceljs y plantilla configurada. |
| exportETPAsWordC | Exporta el ETP a Word usando docx. |
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 5 tools
The tools are mostly distinct: autoCompleteRfCu for document completion, exports to two formats (Excel/Word), and two test generators (E2E/API). The export pair could be confused by name alone, but descriptions clarify the format difference.
All tool names follow a consistent camelCase pattern with verb+object (autoComplete, export, generate). Abbreviations like RfCu, ETP, Excel, Word, E2E, Rest are used consistently. No mixing of styles.
5 tools is well-scoped for a QA server covering document management, export, and test generation. Not too few or too many.
The tools cover test preparation and generation but lack execution, reporting, or defect management. Could be more complete for a QA server, but covers core generation tasks.