Discover and map the entire Cypress test suite. Returns all specs with test counts, describe blocks, and test names. Use this first to understand what tests exist before writing or running anything.

Deep analysis of a single spec file. Extracts describe/it blocks with line numbers, cy.visit URLs, cy.intercept routes, fixtures used, and custom commands called.

List all Cypress spec files in the project. Returns file paths and test counts.

Run a single Cypress spec file headless. Returns structured results with pass/fail counts, failure details, screenshot paths, and recommended next actions.

Run a specific test by name within a spec file using grep. Returns structured results with recommended next actions for the agent.

Replay the exact last run_spec or run_test invocation. Removes friction when iterating on the same failure — no need to reconstruct arguments.

Return the full structured results of the most recent Cypress test run including runId, args used, and all test details.

Get a compact debugging bundle for the most recent failure. Returns the failing test, error, stack hint, screenshot paths, relevant spec excerpt, and recommended next actions. This is the key tool for the fix-and-rerun loop.

Find screenshot files from Cypress test failures. Returns absolute file paths that multimodal AI agents can read directly.

Return the contents of cypress.env.json with sensitive values masked. Safe to display.

Comprehensive health check of the Cypress project. Validates config file, binary, spec files, support file, and directories. Use this to diagnose setup issues.