Cypress Cloud MCP Server

Content

Cypress Cloud MCP Server is Cypress' official remote Model Context Protocol server for agentic debugging and quality workflows. It connects AI coding tools to Cypress Cloud so Claude can query real-time test run context, summarize failures, identify flake patterns, retrieve Test Replay links, and inspect Accessibility or UI Coverage data when those products are available to the organization.

The Cypress documentation says Cloud MCP reached general availability on 2026-05-20 and is included on every Cypress Cloud plan at no additional cost. Access is controlled through organization enablement plus per-user OAuth or a personal access token. OAuth is the recommended setup path when the MCP client supports browser-based authentication.

Source Review

• https://docs.cypress.io/cloud/integrations/cloud-mcp
• https://docs.cypress.io/cloud/features/cypress-ai-features
• https://github.com/cypress-io/ai-toolkit
• https://github.com/cypress-io/ai-toolkit/blob/main/README.md
• https://github.com/cypress-io/ai-toolkit/blob/main/mcp/README.md
• https://github.com/cypress-io/ai-toolkit/blob/main/mcp/.mcp.claude.json
• https://github.com/cypress-io/ai-toolkit/blob/main/mcp/.mcp.cursor.json
• https://github.com/cypress-io/ai-toolkit/blob/main/LICENSE

These sources were reviewed on 2026-06-06. Prefer the live Cypress Cloud MCP documentation and the official Cypress AI Toolkit repository for current setup commands, supported clients, authentication behavior, tool names, and plan availability.

Features

• Remote HTTP MCP server hosted by Cypress.
• OAuth setup for clients that support browser-based authentication.
• Personal access token fallback for clients that do not support OAuth.
• Project discovery with cypress_get_projects.
• Run summaries with project name, run number, status, run URL, tags, and test status counts.
• Failed test details including test names, spec files, attempt errors, stack traces, and Test Replay links.
• Flaky test lookup for distinguishing known flake from likely regressions.
• Cypress Accessibility report summaries, view-level browsing, and rule failure details.
• UI Coverage report summaries, view-level browsing, and tested or untested element details.
• Agent feedback path through cypress_feedback.

Installation

Enable Cloud MCP for the Cypress Cloud organization first, then authenticate as the user whose Cloud permissions should apply.

For Claude Code with OAuth:

claude mcp add cypress-cloud https://mcp.cypress.io/mcp --transport http

Start a Claude Code session, use /mcp, and complete the Cypress Cloud browser sign-in when prompted.

For clients that support JSON remote MCP configuration:

{
  "mcpServers": {
    "cypress-cloud": {
      "type": "http",
      "url": "https://mcp.cypress.io/mcp"
    }
  }
}

For clients that need a personal access token, keep the token in an environment variable or approved secret store:

{
  "mcpServers": {
    "cypress-cloud": {
      "type": "http",
      "url": "https://mcp.cypress.io/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_CYPRESS_MCP_TOKEN"
      }
    }
  }
}

Use Cases

• Ask Claude for a high-level summary of the latest Cypress Cloud run on the current branch.
• Pull failed test details and Test Replay links before fixing a regression.
• Compare recent run failures to known flaky tests.
• Summarize critical or serious Accessibility violations by rule and impacted view.
• Find untested interactive elements from UI Coverage reports.
• Standardize agentic debugging prompts for Cypress-heavy teams.
• Let an assistant gather test evidence before a human reviews the proposed code or test change.

Safety and Privacy

Cypress Cloud MCP exposes live quality and debugging data to the connected AI client. Treat it as access to Cypress Cloud, not as a generic public testing tool. The assistant may see branch names, run URLs, stack traces, selectors, view names, failure messages, and replay links that reveal internal product behavior.

Keep OAuth sessions and MCP personal access tokens scoped to approved users. Use the Cypress Cloud profile page to revoke OAuth sessions or rotate PATs when needed. Require human review before acting on model-suggested fixes, filing feedback to Cypress, or sharing run/replay details outside the engineering team.

Duplicate Check

No mcp.cypress.io, Cypress Cloud MCP, or cypress-io/ai-toolkit MCP entry was found in content/mcp, content/tools, content/guides, or content/agents.