Mobile QA Helper

What is Mobile QA Helper?

Mobile QA Helper is a Model Context Protocol (MCP) server for mobile automation teams. It provides structured, reusable QA prompt templates that integrate directly with Cursor, enabling predefined workflows for automation development, debugging, and bug reporting via slash commands in chat.

How to use Mobile QA Helper?

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.

Key features of Mobile QA Helper

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

Use cases of Mobile QA Helper

• Mobile automation engineers converting manual test cases to production-ready automation code.
• QA leads reviewing and refactoring existing automation frameworks for consistency and quality.
• Teams analyzing test failures to quickly identify root causes and reduce flakiness.
• Organizations standardizing bug reporting to ensure consistent, professional documentation.

FAQ from Mobile QA Helper

Does Mobile QA Helper require cloning the repository?

No. You do not need to clone the repository; simply configure Cursor MCP to use npx pointing to the GitHub repository.

What transport does Mobile QA Helper use?

It uses stdio transport for integration with Cursor.

What are the runtime requirements?

For end users, npx (part of Node.js) is required. For local development, the server uses TypeScript, @modelcontextprotocol/sdk (v1.27+), and Zod v4.

Can I modify the server locally?

Yes. You can clone the repository, install dependencies, build the project, and start it locally. For development with auto-reload, use the dev script (requires tsx).

What inputs does each prompt require?

Each prompt has specific required and optional fields. For example, /convert-manual-to-automation requires featureNavigation and manualTestCase, with optional existingCode. /xml-to-pom-locators requires pageSourceXml. Refer to the prompt input requirements in the README for full details.