MCP QA 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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| qa_run_testsA | Run QA tests for a project. Loads .mcp-qa-config.json from the project path, executes the configured test modules, and returns a formatted report. Optionally filter by module names or test name substring. |
| qa_run_moduleA | Run a single QA test module for a project. Use this for targeted testing of a specific area (e.g. just API tests or just VM checks). |
| qa_list_modulesA | List available QA testing modules. If a projectPath is provided, also shows which modules are enabled for that project. |
| qa_check_configA | Validate a project's .mcp-qa-config.json file. Returns validation results with specific error messages and line numbers if invalid. |
| qa_get_reportB | Retrieve the last test report for a project. Optionally specify a different output format than what the config defaults to. |
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 5 tools
Each tool serves a distinct purpose: validating config, retrieving reports, listing modules, running specific modules, and running full test suites. There is no overlap or ambiguity.
All tool names follow a consistent 'qa_verb_noun' pattern (e.g., qa_check_config, qa_run_tests), making them predictable and easy to understand.
Five tools is well-scoped for a QA-focused server, covering essential operations without being excessive or insufficient.
The tool set covers the core workflow: configuration validation, module listing, selective or full test execution, and report retrieval. No obvious gaps for the given domain.