Skip to main content
Glama
guyco6742

cypress-runner-mcp

by guyco6742
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to cypress-runner-mcp

No user-submitted related servers found.

    Related Servers

    • cypress-mcp

      yashpreetbathla
      A
      license
      Not graded
      quality
      D
      maintenance
      Exposes Cypress as AI-usable tools for running tests, managing spec files, taking accessibility snapshots, and automating a browser via Playwright-core.
      733 npm
      12
      Business Source 1.1

    • TestPilot MCP

      Kirit2121
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI models (Claude, ChatGPT, GitHub Copilot) to run and analyze local tests, rerun failures, and orchestrate QA workflows using existing UI and API test frameworks.
      6 npm
      MIT

    • cypress-mcp

      jams4code
      A
      license
      A
      quality
      D
      maintenance
      MCP 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.
      11
      733 npm
      Business Source 1.1

    • QA Testing MCP Server

      jpa012401
      F
      license
      A
      quality
      D
      maintenance
      Enables AI agents to perform comprehensive web application testing including visual, functional, performance, accessibility, and SEO analysis using browser automation without requiring API keys.
      7
      -
    • Tesults MCP by tesults

      Tesults MCPofficial

      tesults
      A
      license
      Not graded
      quality
      D
      maintenance
      Connect AI agents to your test results, insights, and targets. Query test runs, failures, flaky tests, and regressions across frameworks including Playwright, Jest, Pytest, Cypress and more.
      23 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 8 tools

    Disambiguation4/5

    Each tool targets a distinct part of the Cypress workflow: running, stopping, checking status, getting output, listing specs, and managing artifacts. Status and output overlap slightly since status mentions recent output, but their intended separation is clear.

    Naming Consistency4/5

    All tools share the cypress_ prefix and mostly follow a verb_noun pattern like cypress_run_spec and cypress_list_specs. cypress_status and cypress_output are noun-oriented rather than verb-oriented, but the overall pattern remains predictable.

    Tool Count5/5

    Eight tools is well-scoped for a Cypress runner server. Each tool covers a necessary part of the execution lifecycle without redundancy or bloat.

    Completeness4/5

    The surface covers running specs, running all tests, stopping, checking status, retrieving output, listing specs, and managing failure artifacts. Minor gaps exist around detailed result reporting or video retrieval, but core workflows are fully supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources