The QA Prompts MCP Server is a Model Context Protocol (MCP) server designed specifically for mobile automation teams. It provides structured, reusable QA prompt templates that can be used directly inside Cursor to streamline automation development, debugging, and bug reporting.
It integrates with Cursor through MCP, allowing teams to trigger predefined QA workflows using simple slash commands in chat.
What It Does
This MCP server offers ready-to-use prompts for:
Converting manual test cases into automation code
Reviewing and refactoring automation frameworks
Analyzing test failures
Standardizing bug reports
Generating Page Object Model (POM) locators from Appium Inspector XML
All outputs are structured and formatted to match professional QA standards and framework conventions.
How to Use It in Cursor (No Repository Clone Required)
You don’t need to clone the repository to use it.
Simply add the server configuration to your Cursor MCP configuration file located at:
~/.cursor/mcp.json
Add this configuration:
Use npx
Point to the GitHub repository: swapnilGirishPawar/Custom-MCP-Server-Mobile-QA
After saving the configuration, restart Cursor. The QA prompts will then appear in chat when you type /.
Available Prompts
- Manual to Automation Conversion
These prompts help automation engineers generate or improve test code:
/convert-manual-to-automation Converts manual test cases into complete Appium + Java + TestNG automation scripts following Page Object Model (POM) architecture.
/refactor-automation-code Performs a detailed PR-style review of automation code and returns a structured improvement report.
/xml-to-pom-locators Converts Appium Inspector page source XML into properly prioritized POM locator declarations (ID → Accessibility ID → XPath).
- Debugging & Failure Analysis
/analyze-test-failure Analyzes Appium failure logs to determine:
Root cause
Severity
Flakiness risk
Fix recommendations
This helps teams quickly understand why a test failed and how to resolve it.
- Bug Standardization
/standardize-bug-report Converts a simple bug description into a fully structured bug report using a standardized organization template.
This ensures consistent, professional bug documentation.
How the Workflow Looks in Cursor
Open Cursor chat (Cmd+L) or Composer (Cmd+I)
Type /
Select one of the available QA prompts
Fill in the required inputs
Submit
The AI processes the structured template and returns formatted, production-ready output.
Example Workflows Standardizing a Bug
You type:
/standardize-bug-report
Provide:
bugDescription: “login button not working on iOS after update”
additionalContext (optional): Build 2.3.1, iPhone 15, Premium account
The system generates:
Proper bug title
Detailed issue description
Reproduction steps
Expected result
Structured formatting
Converting a Manual Test Case to Automation
You type:
/convert-manual-to-automation
Provide:
featureNavigation (e.g., Settings → Notifications → Push Notifications)
manualTestCase (your test steps)
existingCode (optional Page Objects or BaseTest)
The system generates:
Complete TestNG test class
Proper annotations
POM-based implementation
Framework-aligned structure
Prompt Input Requirements
Each prompt requires specific inputs:
convert-manual-to-automation
Required: featureNavigation, manualTestCase
Optional: existingCode
refactor-automation-code
Required: code
xml-to-pom-locators
Required: pageSourceXml
analyze-test-failure
Required: failureLogs
standardize-bug-report
Required: bugDescription
Optional: additionalContext
Local Development Setup
If you want to modify or extend the MCP server:
Clone the GitHub repository
Install dependencies using npm
Build the project
Start it locally
For development with auto-reload, use the dev script (requires tsx).
To test locally before pushing changes, you can point your Cursor MCP configuration to your local build output (dist/index.js) instead of the GitHub source.
Tech Stack
The server is built using:
TypeScript (strict mode enabled)
@modelcontextprotocol/sdk (v1.27+)
Zod v4 for input validation
stdio transport for integration with Cursor
Summary
The QA Prompts MCP Server acts as a structured QA assistant embedded inside Cursor. It eliminates repetitive prompt writing and standardizes automation generation, debugging, and bug documentation workflows.
It’s particularly useful for:
Mobile automation engineers
QA leads
Teams using Appium + Java + TestNG
Organizations aiming for consistent bug reporting standards
Server Config
{
"mcpServers": {
"qa-prompts": {
"command": "npx",
"args": [
"-y",
"github:swapnilGirishPawar/Custom-MCP-Server-Mobile-QA"
]
}
}
}Recommend Servers
View All高德地图官方 MCP Server
Playwright MCP server
summarize chat message