Mobile QA Helper

by swapnilGirishPawar

108 downloads
Not rated
GitHub

Description

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…

About

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…

Details

Author
swapnilGirishPawar
Downloads
108
Categories
Other

- Converts manual test cases into Appium + Java + TestNG automation scripts following POM architecture.
- Performs PR-style automation code review and returns structured improvement reports.
- Converts Appium Inspector page source XML into properly prioritized POM locators.
- Analyzes Appium failure logs to determine root cause, severity, flakiness risk, and fix recommendations.
- Standardizes simple bug descriptions into fully structured bug reports using an organization template.

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

  1. Download and install Highlight from highlightai.com/download
  2. Navigate to the plugins tab and select "Add Custom Plugin"
  3. Configure the plugin with the settings below
    Plugin Name Mobile QA Helper
    Command (node, npx, python, etc.)

    Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.

  4. Enable "Start Automatically" if you want the plugin to start when Highlight launches

From the repository

Add the server configuration to your Cursor MCP configuration file (~/.cursor/mcp.json) using npx, pointing to the GitHub repository swapnilGirishPawar/Custom-MCP-Server-Mobile-QA. Restart Cursor, then type / in chat to select one of the available QA prompts, provide the required inputs, and submit.

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "mobile qa helper": {
            "qa-prompts": {
                "command": "npx",
                "args": [
                    "-y",
                    "github:swapnilGirishPawar/Custom-MCP-Server-Mobile-QA"
                ]
            }
        }
    }
}

McpServers

{
    "qa-prompts": {
        "command": "npx",
        "args": [
            "-y",
            "github:swapnilGirishPawar/Custom-MCP-Server-Mobile-QA"
        ]
    }
}

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
1. 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).

2. 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.

3. 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

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.