Developer toolsPublic source

Test Runner MCP Server

Let your AI agents run tests. This MCP server auto-detects your test framework and runs unit tests, integration tests, browser tests, and coverage — then reports results the agent can act on.

Open the source Read the official guide ↗

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

Provides test capabilities through a typed MCP contract.

Provides runner capabilities through a typed MCP contract.

Architecture

How Test Runner MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

→

MCP client

Discovers schemas, sends calls, and receives typed content.

→

Test Runner MCP Server

Validates the request and owns 7 documented tool contracts.

→

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: ADK MCP SDK + rmcp

Test Runner MCP Server architecture diagram from its official repository

Tool catalog

What can an agent ask Test Runner MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

7 named tools

run_unit_tests

Run unit tests — auto-detects framework (cargo test, pytest, jest, go test)

read only

run_integration_tests

Run integration tests — looks for tests/ directory or integration markers

read only

run_e2e_tests

Run browser/E2E tests (Playwright, Cypress, Selenium)

read only

run_specific_tests

Run specific tests by name — targeted regression testing

read only

get_results

Get results from the last test run (pass/fail counts, failed test names)

read only

get_coverage

Get test coverage report (cargo-tarpaulin, coverage.py, c8)

read only

get_test_logs

Collect test output logs, including stdout/stderr from failed tests

read only

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

7 read only

The registry manifest declares read only tool risk classes.

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

The current README concentrates on its tool surface. Check the source and release notes before relying on optional MCP capabilities beyond tool discovery and invocation.

ADK MCP SDKrmcpRegistry manifest

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install

cargo install mcp-test-runner

ADK-Rust connection shape

let toolset = McpToolset::from_stdio(
    "mcp-test-runner",
    ["mcp-test-runner"],
).await?;

let agent = LlmAgentBuilder::new("agent")
    .tools(toolset.tools().await?)
    .build()?;

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Overview ↗README.md CHANGELOG ↗CHANGELOG.md Architecture ↗docs/architecture.svg Issues and support ↗github.com issues

Keep exploring