QA Prompts MCP Server
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
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| convert-manual-to-automationB | Converts manual test cases into well-structured Appium + Java + TestNG automation scripts following POM architecture. |
| refactor-automation-codeC | Performs a deep technical PR review of Appium + Java + TestNG automation code and generates a professional PR Review Report. |
| xml-to-pom-locatorsA | Converts Appium Inspector Page Source XML into POM locator declarations with proper locator strategy priority (ID > Accessibility > XPath). |
| analyze-test-failureA | Performs deep failure analysis of Appium test logs to determine the true root cause, classify severity, assess flakiness risk, and provide fix recommendations. |
| standardize-bug-reportB | Converts a bug title or description into a properly structured, standardized bug report following the organization's template. |
| Automation-initialization-codeB | Returns the prompt text to generate Java test and page classes matching src/test/java/testsuite, for class name: required. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| convert-manual-to-automation | Converts manual test cases into well-structured Appium + Java + TestNG automation scripts following POM architecture. |
| refactor-automation-code | Performs a deep technical PR review of Appium + Java + TestNG automation code and generates a professional PR Review Report. |
| xml-to-pom-locators | Converts Appium Inspector Page Source XML into POM locator declarations with proper locator strategy priority (ID > Accessibility > XPath). |
| analyze-test-failure | Performs deep failure analysis of Appium test logs to determine the true root cause, classify severity, assess flakiness risk, and provide fix recommendations. |
| standardize-bug-report | Converts a bug title or description into a properly structured, standardized bug report following the organization's template. |
| Automation-initialization-code | Produces scaffold Java test and page classes matching src/test/java/testsuite architecture, using a required class name. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: converting page source, analyzing failures, formatting bug reports, generating initialization code, converting manual tests, and reviewing code. No overlap.
Five tools follow a consistent hyphen-separated lowercase pattern (e.g., xml-to-pom-locators), but 'Automation-initialization-code' starts with a capital letter, breaking the pattern.
With 6 tools, the set covers the core QA automation workflow—locator generation, failure analysis, bug reporting, test generation, manual conversion, and code review—without being too sparse or bloated.
The tools cover the main stages of Appium automation: setup, analysis, reporting, and refactoring. Missing potential tools like test data generation or execution, but the scope is reasonable.