mcp-test-runner
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| healthD | – |
| run_pytestD | – |
| run_jestD | – |
| run_single_testD | – |
| parse_test_outputD | – |
| get_coverage_summaryD | – |
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 6 tools
The tool names clearly differentiate between different testing frameworks (pytest vs jest), single test execution, output parsing, coverage, and health. Without descriptions, there is slight potential confusion between run_pytest and run_single_test, but names are sufficiently distinct.
Three tools use the 'run_' prefix (run_pytest, run_jest, run_single_test), but parse_test_output, get_coverage_summary, and health deviate. The pattern is mixed but still readable and not chaotic.
With 6 tools, the server covers essential test runner operations: running tests by framework, running a single test, parsing output, coverage, and health check. Each tool serves a distinct purpose without unnecessary bloat.
The tool set covers core testing workflows: running tests (multiple frameworks), analyzing results (parse output, coverage), and health monitoring. Minor gaps like a combined test runner or report generation exist but do not hinder basic usage.