cypress-mcp
Allows AI coding agents to run, debug, and iterate on Cypress E2E tests directly, including executing spec files, rerunning tests, retrieving failure context and screenshots, and discovering test suites.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@cypress-mcprun the login spec and show me the failures"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
cypress-mcp
MCP server that gives AI coding agents full control over Cypress test execution.
Run, debug, and iterate on E2E tests directly from Claude Code, Cursor, Windsurf, or any MCP-compatible agent — without switching to a terminal.
Install
Package Manager | Command |
npx (no install) |
|
npm |
|
pnpm |
|
yarn |
|
bun |
|
From GitHub |
|
Related MCP server: cypress-mcp-server
Quick Start
Register with your MCP client:
Claude Code:
claude mcp add cypress-mcp -- npx cypress-mcp --cwd /path/to/projectCursor / VS Code:
{
"mcpServers": {
"cypress": {
"command": "npx",
"args": ["cypress-mcp", "--cwd", "/path/to/your/project"]
}
}
}Windsurf:
{
"mcpServers": {
"cypress": {
"command": "npx",
"args": ["cypress-mcp", "--cwd", "/path/to/your/project"]
}
}
}Why
AI agents can write Cypress tests but can't run them. Every change requires you to switch to terminal, run npx cypress run, wait, copy the output back. This kills iteration speed.
cypress-mcp closes the loop. The agent runs specs, reads failures, views screenshots, inspects crash context, reruns the last command, and discovers the test suite — all within the conversation.
Tools (11)
Core Loop
Tool | What it does |
| Run a spec file headless, get structured JSON results |
| Run a single test by name (grep filter) |
| Replay the exact last run without rebuilding arguments |
| List all spec files with test counts |
Debug
Tool | What it does |
| Compact debugging bundle: error, stack, spec excerpt, screenshots, next actions |
| Find failure screenshots by spec or test name |
| Full results of the most recent run |
Discovery
Tool | What it does |
| Map the entire test suite: specs, test names, counts |
| Deep-parse a spec: describe blocks, visits, intercepts, fixtures |
Setup
Tool | What it does |
| Show cypress.env.json (secrets masked) |
| Health check: config, binary, specs, support file, directories |
How It Works
graph LR
A[AI Agent] -->|stdio JSON-RPC| B[cypress-mcp]
B -->|child_process.spawn| C[Cypress Runtime]
C -->|JSON reporter| B
B -->|structured result| A
style A fill:#1a1a2e,stroke:#e94560,color:#fff
style B fill:#16213e,stroke:#0f3460,color:#fff
style C fill:#0f3460,stroke:#533483,color:#fffstdio transport — the agent spawns the server as a child process
Serial execution — one Cypress run at a time, no concurrency
Structured output — JSON results with failure details, diffs, screenshot paths
Config-aware — auto-detects
cypress.config.*, follows relative imports, respects custom pathsCross-platform — Windows, macOS, Linux
Agent Workflow
graph TD
D[cypress_discover] -->|map test suite| E[cypress_analyze_spec]
E -->|understand spec| F[cypress_run_spec]
F -->|tests fail| G[cypress_get_failure_context]
G -->|error + excerpt + screenshots| H[Fix the code]
H -->|iterate| I[cypress_rerun_last]
I -->|still failing| G
I -->|passing| J[Done]
F -->|tests pass| J
style D fill:#1a1a2e,stroke:#e94560,color:#fff
style F fill:#16213e,stroke:#0f3460,color:#fff
style G fill:#e94560,stroke:#fff,color:#fff
style I fill:#0f3460,stroke:#533483,color:#fff
style J fill:#2d6a4f,stroke:#40916c,color:#fffConfiguration
Works out of the box for standard Cypress projects. For custom setups, create cypress-mcp.config.json:
{
"defaultBrowser": "chrome",
"defaultTimeout": 600000,
"cypressConfigFile": "config/cypress.config.ts",
"specPattern": ["e2e/**/*.cy.ts"],
"supportFile": "support/e2e.ts",
"titleFilterSupport": true,
"screenshotsDir": "cypress/screenshots"
}Supported Versions
Cypress 12.x — 15.x
Node.js 18+
Windows, macOS, Linux
Registry Status
Registry | Package | Status |
npm | Published | |
GitHub | Source |
Development
git clone https://github.com/jams4code/cypress-mcp.git
cd cypress-mcp
npm install
npm run build
npm testLicense
Business Source License 1.1 — free for individuals, education, and open source. Commercial production use requires a license. See LICENSING.md for details.
Converts to Apache 2.0 on March 25, 2029.
Licensed by JADEV GROUP SARL (BE1027.114.687), Brussels, Belgium.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/jams4code/cypress-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server