Unit Tests MCP Guide

Isolated, deterministic unit tests across Jest, Vitest, JUnit, pytest, and similar frameworks.

Overview

The Unit Tests MCP supports unit test generation and improvement across multiple languages and frameworks. It analyzes the existing test setup, proposes an architecture that fits, and generates isolated, deterministic, behavior-focused tests.

Use this MCP for new unit test creation, coverage-driven test plans, regression tests for specific bugs, or non-invasive recommendations against existing suites.

URLs and JSON

Mount: /mcp/v2/unit_tests. Config key: qe_unit_tests_v2.

Environment	URL	Transport	Status
Development	`https://qe-mcp.bindg.com/mcp/v2/unit_tests`	http	V2
Production	`https://qe-mcp.bindg.com/mcp/v2/unit_tests`	http	V2

Cursor — `~/.cursor/mcp.json`

{
  "mcpServers": {
    "qe_unit_tests_v2": {
      "url": "https://qe-mcp.bindg.com/mcp/v2/unit_tests",
      "transport": "http"
    }
  }
}

VS Code — `.vscode/mcp.json`

{
  "servers": {
    "qe_unit_tests_v2": {
      "url": "https://qe-mcp.bindg.com/mcp/v2/unit_tests",
      "type": "http"
    }
  },
  "inputs": []
}

Tools

Tool	What it does
`unit_test_core`	Generates isolated, AAA-structured unit tests (Python, JS/TS, Java, C#, Go, Rust). Non-destructive writes to `tests/recommended/` when tests already exist.
`unit_test_coverage`	Measures coverage, inventories infrastructure, finds blind spots, and produces a `tests/recommended/` improvement package. Hand off to `unit_test_core` to implement.
`unit_test_mutation`	File-scoped mutation testing (PITest, Stryker, Mutmut, and others). Scores effectiveness via killed vs survived mutants; confirm-before-apply remediation only.

Add to Cursor

Open Cursor Settings and search for Tools & MCP.
Choose New MCP Server.
Paste the JSON above (or add a single entry).
Save and confirm the server appears connected.

Add to VS Code

Open the Command Palette and search for MCP: Add Server.
Select HTTP.
Enter the URL https://qe-mcp.bindg.com/mcp/v2/unit_tests.
Provide an alias such as qe_unit_tests_v2.
Save globally or to the workspace and start the server.

Generation workflow

1. Analyze repo and unit test framework

Identify language and runtime.
Detect framework: Jest, Vitest, JUnit, pytest, or similar.
Locate test configuration and existing structure.
Find test utilities, mocks, fixtures, and setup files.

2. Propose unit test architecture

Adapt to existing conventions.
Define mock strategy.
Identify coverage approach.
Avoid forcing a new structure where one already exists.

3. Generate unit tests

Keep tests isolated, deterministic, fast, and readable.
Use Arrange / Act / Assert.
Focus on behavior, not implementation details.
Cover normal, edge, and failure cases.
Target 80%+ coverage for main modules and higher coverage for critical logic.

When existing unit tests are already present, recommended improvements are generated non-invasively under tests/recommended/ unless the developer asks for edits. Use unit_test_coverage and unit_test_mutation before or after unit_test_core when you want coverage or mutation feedback.

Unit test rules

High-quality tests over superficial coverage.
Isolated and deterministic tests.
Mocks and stubs at boundaries.
No external dependencies.
Behavior-focused assertions.
AAA structure.
Edge and failure coverage.
Measurable 80%+ coverage for main modules, higher for critical logic.

Example prompts

Detect setup: Using MCP server qe_unit_tests_v2, detect the unit test framework, test structure, and existing mocks/fixtures/setup. Summarize current conventions and how new tests should fit in.

Generate high-quality tests: Using MCP server qe_unit_tests_v2, generate high-quality unit tests for <module path> using AAA, isolated mocks at boundaries, and behavior-focused assertions. Do not modify existing tests unless I ask.

Coverage: Using MCP server qe_unit_tests_v2, run unit_test_coverage on this repo and propose a non-destructive improvement package.

Mutation: Using MCP server qe_unit_tests_v2, run mutation testing on <file> and propose stronger tests (confirm before apply).

Regression test: Using MCP server qe_unit_tests_v2, write a regression unit test for this bug: <describe bug>. Make the test fail first, then describe the minimal fix.

BBVPN proxy configuration

This MCP is hosted on qe-mcp.bindg.com. If you are on BBVPN, add qe-mcp.bindg.com to your IDE's http.noProxy setting (not in mcp.json).

{
  "http.noProxy": [
    "qe-mcp.bindg.com"
  ]
}

Validate the connection

Smoke test: Using my MCP server qe_unit_tests_v2, list available tools or capabilities and provide a short ready checklist.

← Back to MCP Server Guide ← Back to Quality Engineering Tools Suite