QA Testing MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@QA Testing MCP Server Run a full QA test on https://example.com"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
QA Testing MCP Server
An AI-driven testing and QA MCP (Model Context Protocol) server that enables AI agents like Claude, Claude Code, or Cursor to perform comprehensive web application testing without requiring API keys.
Features
Visual Testing: Screenshot capture, responsive design analysis, layout consistency checks
Functional Testing: Form validation, link integrity, interactive element testing, navigation analysis
Performance Testing: Core Web Vitals measurement, resource analysis, optimization opportunities
Accessibility Testing: WCAG compliance (A, AA, AAA), color contrast, ARIA validation
SEO Analysis: Meta tags, heading structure, content analysis, technical SEO
Report Generation: Comprehensive Markdown reports with prioritized recommendations
Related MCP server: Browser-Debugger
Architecture
┌─────────────────────────────────────────────────────────────────┐
│ User (Cursor/Claude) │
│ "Test https://example.com" │
└─────────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────────┐
│ QA Testing MCP Server │
│ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ ┌───────────┐ │
│ │ Visual │ │ Functional │ │ Performance │ │Accessibility│ │
│ │ Testing │ │ Testing │ │ Testing │ │ Testing │ │
│ └─────────────┘ └─────────────┘ └─────────────┘ └───────────┘ │
│ ┌─────────────┐ ┌─────────────┐ ┌─────────────────────────────┐ │
│ │ SEO │ │ Report │ │ Full Test Suite Runner │ │
│ │ Analysis │ │ Generator │ │ │ │
│ └─────────────┘ └─────────────┘ └─────────────────────────────┘ │
└─────────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────────┐
│ chrome-devtools-mcp │
│ (Browser automation & inspection) │
└─────────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────────┐
│ Chrome Browser │
│ (Web application under test) │
└─────────────────────────────────────────────────────────────────┘Prerequisites
Node.js v22.12.0 or newer
npm (comes with Node.js)
Chrome browser (stable, beta, or canary)
Cursor IDE or Claude with MCP support
Installation
1. Clone and Build
# Clone the repository
git clone <repository-url>
cd emerge
# Install dependencies
npm install
# Build the project
npm run build2. Configure MCP Servers
Add the following to your MCP client configuration:
For Cursor (Settings → MCP → Add Server):
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": ["chrome-devtools-mcp@latest"]
},
"qa-testing": {
"command": "node",
"args": ["/absolute/path/to/emerge/dist/index.js"]
}
}
}For Claude Desktop (claude_desktop_config.json):
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": ["chrome-devtools-mcp@latest"]
},
"qa-testing": {
"command": "node",
"args": ["/absolute/path/to/emerge/dist/index.js"]
}
}
}3. Verify Installation
After configuring, restart your MCP client and verify the tools are available:
List all available MCP toolsYou should see tools like run_visual_test, run_performance_test, run_full_test, etc.
Usage
Quick Start
Simply ask the AI to test a website:
Test https://example.com and generate a full QA reportAvailable Tools
Tool | Description |
| Screenshots, viewport analysis, layout checks |
| Forms, links, interactions, navigation |
| Core Web Vitals, resource metrics |
| WCAG compliance, ARIA, contrast |
| Meta tags, headings, technical SEO |
| All tests + comprehensive report |
| Compile results into Markdown report |
Example Prompts
Full Test Suite:
Run a comprehensive test on https://mywebsite.com including visual, functional, performance, accessibility, and SEO analysis. Generate a detailed report.Specific Testing:
Check the accessibility of https://mywebsite.com against WCAG 2.1 Level AA standards.Analyze the performance of https://mywebsite.com - measure Core Web Vitals and identify optimization opportunities.Test the mobile responsiveness of https://mywebsite.com at 375px, 768px, and 1440px viewports.Combined with chrome-devtools-mcp:
Navigate to https://mywebsite.com, take screenshots at mobile and desktop sizes, then run a performance trace and accessibility check. Generate a report with all findings.See sample-prompts/test-prompts.md for more example prompts.
Report Structure
Generated reports include:
# Web Application Test Report
## Executive Summary
- Overall score and status
- Test coverage
- Issues overview (critical, major, minor)
- Key highlights
## Visual Testing Results
- Viewports tested
- Layout issues
- Responsiveness checks
## Functional Testing Results
- Forms analysis
- Links analysis
- Interactive elements
- Navigation structure
## Performance Testing Results
- Core Web Vitals
- Resource metrics
- Optimization opportunities
## Accessibility Testing Results
- WCAG compliance level
- Violations found
- ARIA usage
- Color contrast
## SEO Analysis Results
- Meta tags
- Heading structure
- Content analysis
- Technical SEO
## Recommendations
- High priority
- Medium priority
- Low priority
## Raw Data
- Complete JSON data (collapsible)Chrome DevTools MCP Options
The chrome-devtools-mcp server supports various configuration options:
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": [
"chrome-devtools-mcp@latest",
"--headless=true", // Run headless for CI/CD
"--isolated=true", // Use temporary profile
"--channel=canary" // Use Chrome Canary
]
}
}
}Connect to Running Chrome:
# Start Chrome with remote debugging
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome \
--remote-debugging-port=9222 \
--user-data-dir=/tmp/chrome-profile{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": [
"chrome-devtools-mcp@latest",
"--browser-url=http://127.0.0.1:9222"
]
}
}
}Development
# Install dependencies
npm install
# Build
npm run build
# Watch mode (development)
npm run dev
# Run tests
npm testProject Structure
emerge/
├── package.json # Project configuration
├── tsconfig.json # TypeScript configuration
├── README.md # This file
├── src/
│ ├── index.ts # Entry point
│ ├── server.ts # MCP server implementation
│ ├── tools/
│ │ ├── index.ts # Tool exports
│ │ ├── visual-test.ts # Visual testing
│ │ ├── functional-test.ts# Functional testing
│ │ ├── performance-test.ts# Performance testing
│ │ ├── accessibility-test.ts# Accessibility testing
│ │ └── seo-test.ts # SEO analysis
│ ├── report/
│ │ ├── generator.ts # Report generation
│ │ └── templates.ts # Markdown templates
│ └── types/
│ └── index.ts # TypeScript types
├── prompts/
│ └── test-prompts.md # Example prompts
├── mcp-config.example.json # MCP configuration example
└── cursor-mcp-settings.json # Cursor-specific configHow It Works
User Input: You provide a URL and testing scope through Cursor or Claude
AI Processing: The AI interprets your request and calls the appropriate testing tools
Browser Automation: chrome-devtools-mcp controls Chrome to load pages and gather data
Analysis: Each tool analyzes specific aspects (visual, performance, etc.)
Report Generation: Results are compiled into a comprehensive Markdown report
Recommendations: Prioritized suggestions for improvement
Security Considerations
The chrome-devtools-mcp server exposes browser content to MCP clients
Avoid testing pages with sensitive information during sessions
Use
--isolated=truefor temporary profiles that clear after testingBe cautious with
--remote-debugging-portas it opens browser control
Limitations
Real-time metrics require actual browser automation via chrome-devtools-mcp
Some tests provide guidance for AI to execute rather than direct measurements
Performance metrics are most accurate with multiple test runs
Accessibility testing should be complemented with manual review
Contributing
Contributions are welcome! Please feel free to submit issues and pull requests.
License
MIT License - see LICENSE file for details.
Resources
Available Tools
7 toolsgenerate_reportA
Generate a comprehensive Markdown report from test results. This tool:
Compiles results from all test types (visual, functional, performance, accessibility, SEO)
Calculates overall scores and status
Prioritizes recommendations by impact and effort
Formats results in a readable Markdown report
Use this tool after running individual tests to create a final report. Call run_full_test to automatically run all tests and generate a report in one step.
Inputs: url (required), title.
run_accessibility_testA
Perform accessibility testing on a web application. This tool analyzes:
WCAG 2.1 compliance at Level A, AA, or AAA
Color contrast ratios for text elements
ARIA attributes and landmark usage
Keyboard navigation and focus management
Form labels and error handling
Image alt text and semantic structure
Use this tool when you need to evaluate a website's accessibility for users with disabilities. The tool requires chrome-devtools-mcp to be running for DOM and accessibility tree inspection.
Inputs: url (required), wcagLevel, includeWarnings.
run_full_testB
Run all available tests (visual, functional, performance, accessibility, SEO) on a web application and generate a comprehensive report
Inputs: url (required).
run_functional_testB
Perform functional testing on a web application. This tool analyzes:
Form elements: validation, labels, accessibility
Links: internal/external, broken links detection
Interactive elements: buttons, clickable areas, focus management
Navigation: menu structure, skip links, keyboard navigation
Use this tool when you need to verify that a website's features work correctly. The tool requires chrome-devtools-mcp to be running for browser automation.
Inputs: url (required), checkForms, checkLinks, checkInteractions.
run_performance_testA
Perform performance testing on a web application. This tool measures:
Core Web Vitals: FCP, LCP, CLS, TTI, TBT
Page load timing metrics
Resource analysis: total size, JS/CSS/image sizes
Third-party request impact
Performance optimization opportunities
Use this tool when you need to evaluate a website's loading performance and identify bottlenecks. The tool requires chrome-devtools-mcp to be running for performance tracing.
Inputs: url (required), runs, throttle.
run_seo_testA
Perform SEO analysis on a web application. This tool analyzes:
Meta tags: title, description, canonical, robots, OG tags, Twitter cards
Heading structure: H1 count, hierarchy, semantic structure
Content: word count, text-to-HTML ratio, image optimization
Technical SEO: HTTPS, mobile-friendly, structured data, sitemap
Use this tool when you need to evaluate a website's search engine optimization. The tool requires chrome-devtools-mcp to be running for DOM inspection.
Inputs: url (required), checkSocialTags, checkStructuredData.
run_visual_testA
Perform visual testing on a web application. This tool analyzes:
Screenshots at multiple viewport sizes (mobile, tablet, desktop)
Layout consistency and potential overflow issues
Responsive design implementation
Visual element alignment and spacing
Use this tool when you need to evaluate the visual appearance and responsiveness of a website. The tool requires chrome-devtools-mcp to be running for browser automation.
Inputs: url (required), fullPage, viewports.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 7 tools
Each of the five test tools targets a clearly distinct testing dimension (visual, functional, performance, accessibility, SEO), so misselection is unlikely. The only overlap is run_full_test, which subsumes all individual tests plus generate_report, but the descriptions explicitly clarify when to use each.
Six of seven tools follow the predictable run_<type>_test verb_noun pattern. generate_report breaks the pattern slightly but remains readable and describes a distinct action.
Seven tools is well-scoped for a QA testing server, with one tool per test category plus a runner/report generator. Each tool earns its place without redundancy.
The surface covers the major QA dimensions (visual, functional, performance, accessibility, SEO), a full-suite runner, and report generation, forming a complete workflow. Minor gaps exist around setup/configuration or exporting raw test data, but agents can work around these.
Maintenance
Related MCP Connectors
Hosted browser for AI agents: screenshots, post-JS DOM, console, WCAG. No install, no API key.
Browser-based QA for AI-built software. Test pages with real browsers via agents.
AI QA tester — real browsers scan sites for bugs, SEO, perf, and accessibility issues via chat.
Website checker for AI coding agents. Measures your site in a real browser, with evidence.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI agents to perform comprehensive web accessibility checks (WCAG 2.1/2.2) including color contrast analysis, ARIA validation, and full accessibility report generation without requiring any API key.836 PyPIMIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to automate and debug real Chromium browsers with capabilities like screenshots, video recording, performance analysis, visual regression testing, and OCR text extraction.13-
- AlicenseAqualityBmaintenanceEnables AI agents to drive Playwright-based browser automation for UI testing, returning JSON/HTML reports with screenshots without server-side LLM or test scripts. https://easy-ui-mcp.vercel.app/16261MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to autonomously interact with and test web applications in a real browser, providing DOM/Accessibility tree extraction, runtime telemetry, screenshot capture, and Markdown test reports.9 npm1MIT