Test Gap Analyzer MCP Guide

Compare application features against existing automation and identify missing scenarios, weak coverage areas, and recommended new tests.

Overview

The Test Gap Analyzer MCP maps production code to tests, quantifies gaps, assesses risk/quality, and audits within-suite redundancy. Talk in plain language; the agent picks the right tools. Reports land under .qe/reports/ (safe to delete after review — add .qe/ to .gitignore).

Use this when you want what’s missing, what to test next, whether tests are strong, or whether a folder is bloated. Pair later with Test Spec for plans and E2E V2 to author new Playwright tests.

URL and JSON

Mount: /mcp/v2/test_gap_analyzer. Config key: test_gap_analyzer.

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

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

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

VS Code — `.vscode/mcp.json`

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

Add to Cursor

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

Add to VS Code

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

Tools

You want…	Tool
What’s missing?	`analyze_test_gaps`
How bad are the gaps / what next?	`mitigate_test_gaps` (after a gap report)
Are my tests strong, or just numerous?	`assess_test_quality`
Is this suite bloated or overlapping?	`analyze_test_redundancy`
Gaps + quality + redundancy in one run	Full mode on `analyze_test_gaps` (see below)

Workflows

1. Find gaps, then plan what to do

Ask for a gap analysis on the repo (or a feature area).
Read the gap report (and dashboard/canvas if created).
Ask to mitigate important gaps (risk, edge cases, P0 priorities).
Optionally ask for a quality score on the existing suite.

2. Quality check only

When coverage seems okay but tests feel weak — ask to score assertion strength.

3. Redundancy check

Point at a folder. The agent reports overlaps; it should not remove tests unless you approve.

4. Full analysis

Say clearly that you want a full run and include a test folder for redundancy, for example: “Run a full test gap analysis on tests/e2e/.” You’ll confirm each major step (yes / no / stop).

What you’ll see

Artifact	Meaning
`.qe/reports/test-gap-analysis-….md`	Main gap report
Optional canvas / HTML dashboard	Easier browsing of the same findings
Quality section / quality canvas	Scorecard when you run quality assessment
`.qe/reports/test-redundancy-report-….md`	Overlap / consolidation findings

Example prompts

Gaps: Analyze test gaps in this repo — what’s untested? Using MCP server test_gap_analyzer.

Mitigation: Mitigate the P0 gaps from the latest report.

Quality: Score the quality of our existing unit and E2E tests. Are our assertions weak?

Redundancy: Analyze redundancy in tests/checkout/ — don’t delete anything yet.

Full run: Run a full test gap analysis on tests/e2e/.

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 test_gap_analyzer, list available tools or capabilities and provide a short ready checklist.

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