cypress-runner-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CYPRESS_WORKSPACE | Yes | Absolute path to your Cypress project root directory |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cypress_run_specA | Run a specific Cypress test spec file. Returns immediately and runs in background. |
| cypress_run_allB | Run all Cypress tests in a project |
| cypress_stopA | Stop the currently running Cypress test |
| cypress_statusB | Get current test execution status, including if tests are running and recent output |
| cypress_outputA | Get the full console output from the current or last test run |
| cypress_list_specsA | List all available Cypress spec files in a project |
| cypress_screenshotsB | List or get screenshots from test failures |
| cypress_clear_artifactsA | Clear screenshots and videos from previous test runs |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Live Test Output | Real-time console output from running Cypress tests |
| Test Status | Current test execution status |
TDQS
Scored across 8 tools
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.
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.
Eight tools is well-scoped for a Cypress runner server. Each tool covers a necessary part of the execution lifecycle without redundancy or bloat.
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.