Diagnose Cypress setup issues by validating config file, binary, spec files, support file, and directories. Use this health check to identify and resolve configuration or environment problems.
Business Source 1.1
458,502 tools. Updated 2026-08-17 03:36
"Cypress" matching MCP tools:
- Discover and map all Cypress specs, test counts, describe blocks, and test names to understand the full test suite before writing or running tests.Business Source 1.1
- Find screenshot files from Cypress test failures and get their absolute file paths for direct reading by AI agents.Business Source 1.1
- Retrieve the full structured results from the most recent Cypress test run, including runId, arguments, and detailed test outcomes.Business Source 1.1
- Retrieve test results from a previous Cypress run by specifying the run ID, or get all results if no ID is provided.MIT
- Run a single Cypress spec file headless and get structured results: pass/fail counts, failure details, screenshot paths, and recommended next actions.Business Source 1.1
Matching MCP Servers
- AlicenseAqualityDmaintenanceMCP server that gives AI coding agents full control over Cypress test execution, allowing them to run, debug, and iterate on E2E tests directly from MCP-compatible agents.11505Business Source 1.1
- Alicense-qualityDmaintenanceExposes Cypress as AI-usable tools for running tests, managing spec files, taking accessibility snapshots, and automating a browser via Playwright-core.50510Business Source 1.1
- Opens the Cypress Test Runner in headed mode to interactively debug tests with a selected browser.MIT
- List all Cypress spec files in a project, optionally filtered by a glob pattern. Returns file paths and test counts for quick test discovery.Business Source 1.1
- Run Cypress tests with custom configuration. Specify browser, headless mode, base URL, environment variables, and more to get test results including pass/fail counts and run ID.MIT
- Validate Cypress test files or code for syntax errors and best practices to ensure reliable test automation.MIT
- Generate TypeScript Page Object classes for Cypress testing by analyzing web page URLs to automate test creation and element interaction workflows.MIT
- Execute specific Cypress commands with chaining support, enabling step-by-step test automation and debugging.MIT
- Generate Cypress test files from natural language descriptions to automate test creation.MIT
- Convert completed test cases into executable automation scripts for Playwright, Cypress, Selenium, or Puppeteer. Use after generating test cases to obtain runnable code.MIT
- Create an AI agent with custom personality traits, specializations, and update prompts to handle specific tasks.MIT
- Launch interactive test recording to transcribe browser actions into runnable test code. Use to build baseline happy-path tests by clicking through complex UI flows.MIT
- Execute test suites under the QA runner and generate structured reports with exit codes, logs, and flaky detection. Supports optional filter to target specific tests across pytest, Jest, Cypress, Go, and Maestro.MIT
- Re-run only the tests that failed in the previous run, supporting pytest, Jest, Cypress, Go, and Maestro. Faster than a full suite, ideal for iterative bug fixes.MIT
- Record and update a project's technology stack across categories like backend, frontend, database, infrastructure, testing, and devops, maintaining a central registry for consistency.MIT
- Lists all executable tests in a project using native collection mechanisms (pytest --collect-only, Jest --listTests, etc.). Returns a line-by-line list of node IDs or filenames to verify test coverage before running or generating tests.MIT