Cypress Cloud MCP Server

Remote MCP server from Cypress.io that gives AI assistants read access to Cypress Cloud test runs, failures, flaky tests, accessibility reports, and UI coverage.

Developer Tools by Cypress.io Bearer Token active

Connect (Remote Server) GitHub Docs

Overview

Cypress Cloud MCP is the official Model Context Protocol server hosted by Cypress.io at https://mcp.cypress.io/mcp. It connects AI coding assistants directly to Cypress Cloud so agents can query run statuses, inspect failure details, identify flaky tests, and pull accessibility and UI Coverage reports without developers manually copying stack traces or links into the chat window.

The server exposes read-only tools for projects, runs, failed test details (with Test Replay links), flaky tests, accessibility reports (summary, paginated views, and rule-level failures), and UI Coverage reports (summary, views, and elements). Access is scoped to the user's existing permissions in Cypress Cloud via a personal access token, and the integration must first be enabled by an organization admin.

Cloud MCP works with any AI client that supports remote MCP over HTTP, including Claude, Cursor, GitHub Copilot in VS Code, OpenAI Codex CLI, and Google Antigravity. It is free across all Cypress Cloud plans, including Starter. The related cypress-io/ai-toolkit repository ships complementary AI skills (cypress-author, cypress-explain, cypress-docs) and pre-built Cloud MCP configuration, but the MCP server itself is hosted by Cypress, not self-hosted.

Tools

Tool	Description
`cypress_get_projects`	Lists projects in the organization the user has access to.
`cypress_get_runs`	Retrieves run summaries for a project, optionally filtered by branch or commit URL.
`cypress_get_failed_test_details`	Returns error messages, stack traces, and Test Replay links for failed tests in a run.
`cypress_get_flaky_tests`	Identifies flaky tests detected in a given run or project.
`cypress_get_accessibility_report`	Returns a high-level summary of accessibility violations for a run.
`cypress_get_accessibility_views`	Paginated views of the accessibility report.
`cypress_get_accessibility_rule_failures`	Lists DOM element failures for a specific accessibility rule.
`cypress_get_ui_coverage_report`	Overall UI Coverage scores and the riskiest views in a run.
`cypress_get_ui_coverage_views`	Paginated UI Coverage views for a run.
`cypress_get_ui_coverage_elements`	Per-element interactive coverage details.
`cypress_feedback`	Submits feedback about the MCP experience directly to Cypress.

Setup Guide

Prerequisites

A Cypress Cloud account with the Cloud MCP integration enabled by an org admin (Integrations page in Cypress Cloud)
A personal access token: in Cypress Cloud, click your org picture, go to Manage Profile, and generate a token under "MCP personal access token" (shown only once, copy it)
An AI client that supports remote MCP over HTTP
Node.js v20+ if using mcp-remote (for Claude Desktop)

Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "Cypress Cloud": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://mcp.cypress.io/mcp",
        "--header",
        "Authorization: Bearer ${CYPRESS_MCP_TOKEN}"
      ],
      "env": {
        "CYPRESS_MCP_TOKEN": "YOUR_MCP_TOKEN"
      }
    }
  }
}

Cursor

{
  "mcpServers": {
    "cypress": {
      "url": "https://mcp.cypress.io/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_MCP_TOKEN"
      }
    }
  }
}

VS Code (GitHub Copilot)

{
  "servers": {
    "cypress": {
      "type": "http",
      "url": "https://mcp.cypress.io/mcp",
      "headers": {
        "Authorization": "Bearer ${input:CYPRESS_MCP_TOKEN}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "CYPRESS_MCP_TOKEN",
      "description": "Enter your Cypress MCP personal access token",
      "password": true
    }
  ]
}

Notes

Rate limit: 100 tool requests per hour across all plans
Read-only: cannot modify code, change runs, or delete data
Data retention matches your existing Cypress Cloud recording limits

Use Cases

Triage CI failures from the AI chat by pulling failed test details and Test Replay links for the latest run on a feature branch
Investigate flakiness by asking the agent to list flaky tests for a project and group them by spec or root cause
Generate accessibility remediation tasks from the latest run's accessibility report and rule-level failures
Find UI Coverage gaps by surfacing the riskiest views and untested interactive elements before a release
Summarize the latest main-branch run status (passing, failing, flaky counts) inside a daily standup or PR review workflow

Example Prompts

"List the failed tests in the most recent run on the main branch and include the Test Replay links."
"Which tests have been flaky in the last 10 runs of the checkout project?"
"Show me the accessibility violations from the latest run, grouped by WCAG rule."
"What are the lowest UI Coverage views in our last release run, and which interactive elements were never exercised?"
"Pull the error trace for the failing login.cy.ts test in run 12345 and propose a fix."

Pros

Official, provider-hosted remote MCP server, no self-hosting or local install required
Broad tool coverage across runs, failures, flaky tests, accessibility, and UI Coverage with Test Replay links
Free on all Cypress Cloud plans including Starter
User-scoped personal access tokens inherit existing Cypress Cloud permissions

Limitations

Read-only: cannot trigger runs, modify tests, or delete data
Rate limited to 100 tool requests per hour across all plans
Requires an org admin to enable the integration before individual users can connect

Alternatives

cypress-io/ai-toolkit: Official Cypress AI skills (cypress-author, cypress-explain, cypress-docs) for Claude and Cursor, complementary to Cloud MCP
Community Cypress MCP servers such as yashpreetbathla/cypress-mcp and jams4code/cypress-mcp that focus on local test execution rather than Cloud data
Playwright MCP for teams using Playwright instead of Cypress