# Testing

> Testing is an open-source MCP server for developer tools. MCP server that generates tests, mocks, API stubs and coverage gap reports for AI clients. It runs locally on your machine and is started by your AI client.

- **Kind:** MCP server
- **Pricing:** Open source
- **Platforms:** CLI, API, self-hosted
- **Repository:** https://github.com/rog0x/mcp-testing-tools
- **MCP Registry name:** io.github.rog0x/testing
- **Categories:** [developer tools](https://ai-powered.com/categories/developer-tools)
- **Listing updated:** 2026-11-18

## About

The README describes a set of testing helpers packaged as a Model Context Protocol server, so an AI client can call them as tools during development. Test generation takes a function signature and returns ready-to-run Jest or Vitest code split into happy path, edge, error and boundary cases. Mock helpers produce sample names, emails, addresses, UUIDs, card-style numbers and similar fields, with an English or Spanish locale option.

The server also covers API work: it builds mock JSON responses from a field schema, optionally wrapped in a success/data/meta envelope, and it compares expected and actual JSON to emit per-field assertions. A coverage tool reads source and existing test code and ranks untested functions by export status, complexity estimate, parameter count and whether they are async.

It suits developers who already use an MCP-capable assistant and want it to draft test scaffolding and fixtures. It installs from npm and is released under the MIT licence.

## Features

- **Test case generation:** Creates Jest or Vitest tests from a function signature across happy path, edge, error and boundary categories.
- **Mock data generator:** Produces sample records for fields such as name, email, address, date, phone and IP, with English or Spanish locale.
- **Mock API responses:** Builds JSON payloads for REST endpoints from a field schema, with optional status code and response envelope.
- **Assertion generation:** Diffs expected and actual JSON values and outputs per-field assertions for Jest, Vitest or Chai.
- **Untested function analysis:** Scans source and test code to list functions without tests, prioritised by export status and complexity.

## Good for

- Drafting an initial Vitest suite for a new function from its signature
- Filling a test database with realistic fake customers or contacts
- Stubbing REST endpoints while a backend is still in progress
- Finding which exported functions in a module lack test coverage

## Install

### Claude Code (Terminal)

```sh
claude mcp add testing -- npx -y @rog0x/mcp-testing-tools
```

### Claude Desktop (claude_desktop_config.json)

```json
{
  "mcpServers": {
    "testing": {
      "command": "npx",
      "args": [
        "-y",
        "@rog0x/mcp-testing-tools"
      ]
    }
  }
}
```

### Cursor (~/.cursor/mcp.json)

```json
{
  "mcpServers": {
    "testing": {
      "command": "npx",
      "args": [
        "-y",
        "@rog0x/mcp-testing-tools"
      ]
    }
  }
}
```

### VS Code (.vscode/mcp.json)

```json
{
  "servers": {
    "testing": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@rog0x/mcp-testing-tools"
      ]
    }
  }
}
```

### Windsurf (~/.codeium/windsurf/mcp_config.json)

```json
{
  "mcpServers": {
    "testing": {
      "command": "npx",
      "args": [
        "-y",
        "@rog0x/mcp-testing-tools"
      ]
    }
  }
}
```

### Other clients (your client's MCP settings (most use this shape))

```json
{
  "mcpServers": {
    "testing": {
      "command": "npx",
      "args": [
        "-y",
        "@rog0x/mcp-testing-tools"
      ]
    }
  }
}
```

## Tools

- `generate_tests`: Generate test cases from a function signature as Jest or Vitest code.
- `generate_mock_data`: Generate realistic mock data for testing by type.
- `generate_api_mock`: Generate mock API responses from a schema definition.
- `analyze_test_coverage`: Find untested functions in source code relative to existing tests.
- `generate_assertions`: Generate per-field assertion code by comparing expected and actual values.

## FAQ

### Which test frameworks does it output?

Test generation supports Jest and Vitest, and the assertion tool also supports Chai.

### How is it installed and run?

The README gives npm install and build steps, and shows a Claude Desktop configuration that launches the built server with node.

### What license does it use?

The README states the project is released under the MIT licence.

### Is Testing free?

Yes. Testing is open source, so you can use and self-host it for free.

### How do I add Testing to Claude Code?

Run this command in your terminal: claude mcp add testing -- npx -y @rog0x/mcp-testing-tools

### What are the best alternatives to Testing?

The closest alternatives to Testing are Api Test MCP, Test, Test Intel, Testdino MCP and Testiny Test Management.

## Where this comes from

- Description: written from the project's README and its MCP Registry entry.
- Install steps: from the official MCP Registry entry.

## Alternatives

- [Api Test MCP](https://ai-powered.com/mcp/api-test-mcp): Api Test MCP is an open-source MCP server for developer tools.
- [Test](https://ai-powered.com/mcp/test-2): Test is an open-source MCP server for developer tools.
- [Test Intel](https://ai-powered.com/mcp/test-intel): Test Intel is an open-source MCP server for developer tools.
- [Testdino MCP](https://ai-powered.com/mcp/testdino-mcp): Testdino MCP is an MCP server for developer tools.
- [Testiny Test Management](https://ai-powered.com/mcp/testiny-test-management): Testiny Test Management is a paid MCP server for developer tools.
- [Test Shape MCP](https://ai-powered.com/mcp/test-shape-mcp): Test Shape MCP is an open-source MCP server for developer tools.
- [MCP Failure Lab](https://ai-powered.com/mcp/mcp-failure-lab-2): MCP Failure Lab is an open-source MCP server for developer tools.
- [MCP Server Template](https://ai-powered.com/mcp/mcp-server-template): MCP Server Template is an open-source MCP server for developer tools.

---
Source: https://ai-powered.com/mcp/testing
