QA Testing MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_visual_testA | Perform visual testing on a web application. This tool analyzes:
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. |
| run_functional_testB | Perform functional testing on a web application. This tool analyzes:
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. |
| run_performance_testA | Perform performance testing on a web application. This tool measures:
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. |
| run_accessibility_testA | Perform accessibility testing on a web application. This tool analyzes:
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. |
| run_seo_testA | Perform SEO analysis on a web application. This tool analyzes:
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. |
| generate_reportA | Generate a comprehensive Markdown report from test results. This tool:
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. |
| run_full_testB | Run all available tests (visual, functional, performance, accessibility, SEO) on a web application and generate a comprehensive report |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.