mcp_server

Created By
fulong98a year ago
Overview

what is mcp_server?

mcp_server is a backend server project designed to facilitate the development and deployment of applications.

how to use mcp_server?

To use mcp_server, clone the repository from GitHub, configure the server settings, and run the server command to start the application.

key features of mcp_server?

  • Easy setup and configuration for backend applications.
  • Supports various server commands and parameters for customization.
  • Designed for scalability and performance.

use cases of mcp_server?

  1. Developing RESTful APIs for web applications.
  2. Hosting microservices for distributed systems.
  3. Running backend processes for mobile applications.

FAQ from mcp_server?

  • Is mcp_server suitable for production use?

Yes! mcp_server is designed to be robust and can be used in production environments.

  • How can I contribute to mcp_server?

You can contribute by submitting issues or pull requests on the GitHub repository.

  • What programming languages does mcp_server support?

mcp_server is designed to be language-agnostic, allowing integration with various programming languages.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
fulong98
Star
0
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
10 months ago
Qwen Coding Engine
@neco001

Stop letting AI hallucinations eat your hours. With this engine, your work flows smoothly while a full SRE squad of models codes and debugs on your behalf. Are you building complex applications, only to find that AI hallucinations are eating your entire afternoon? You know the loop: You ask Claude or Cursor to fix a bug. It gives you a snippet. It breaks something else. You paste the error back. It forgets the original architecture and responds with "// ... rest of your code here". What started as a 5-minute feature turns into a 3-hour circular debugging nightmare. If this engine actually works, you are saved. The Qwen Engineering Engine (powered by the Lachman Protocol) completely stops the "two steps forward, one step back" dance. Instead of relying on a single, forgetful LLM to do everything, this MCP Server deploys a dedicated, specialized squad of Qwen models to your local codebase: - Zero Placeholders: The dedicated qwen_coder tool writes 100% complete, production-grade files. No lazy snipping. - Deep Debugging: Instead of pasting logs to Claude, the qwen_audit tool unleashes QwQ (Qwen's reasoning model) to act as your Senior Auditor. It reads the files, finds the memory leak, and tells you exactly what failed. - Architectural Immunity: Before writing code, the qwen_architect drafts a JSON roadmap and self-verifies it against your stack. If it's a bad idea, it rejects it *before* breaking your app. Why Qwen? Because running an entire squad of GPT-4o or Claude 3.5 Opus models to constantly rewrite files would cost you $50 a day. By routing this heavy lifting through Alibaba's DashScope API (Qwen 3.5 Plus & Qwen 2.5 Coder 32B), the cost is literal fractions of a cent. Let your main assistant (Claude/Antigravity/Cursor) be the Commander. Let the Qwen Engine do the heavy lifting in the trenches. Stop chatting. Start shipping.

2 days ago
Mobile QA Helper
@swapnilGirishPawar

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

10 hours ago