Cypress Cloud MCP

io.cypress.mcpPublished by mcp.cypress.ioOfficial publisherv1.0.0Updated Nov 2, 2026

Direct access to Cypress tests results and accessibility reports in your AI workflow.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Remote Cypress Cloud MCP server that gives AI assistants access to your Cypress test results and accessibility reports.

What you can do
  • Read Cypress Cloud test results and accessibility reports from within an AI workflow
  • Inspect data about an application's health and stability in Cypress Cloud
  • Investigate runs, tests, failures, screenshots and Test Replay data (as described for the related Cloud CLI skill)
  • Pair with Cypress AI skills that help author, explain and review Cypress tests
When to use it
Useful for Cypress developers who want their AI coding assistant to look at real Cypress Cloud results, failures and accessibility reports while writing or debugging tests, instead of guessing from generic patterns.
Requirements
A remote endpoint at mcp.cypress.io over streamable HTTP; OAuth sign-in is required by default. A Cypress Cloud account with relevant projects is implied. A Personal Access Token can be used instead of OAuth by editing the agent's .mcp.json.
Before you install
The connection authenticates to your Cypress Cloud account, so the assistant can read your project's test and accessibility data. OAuth is the default; a Personal Access Token alternative means storing that credential in the agent configuration file. The README also describes installing skills and plugins, which is separate from the MCP connection.

Installation

In SourceWeft

  1. Open Cypress Cloud MCP in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.cypress.mcp%2Fcypress-cloud/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

README

[Cypress] [Cypress]

[Discord chat]

✨ Cypress AI Toolkit

Open-source Cypress AI skills, built by the Cypress team. Works with Claude, Cursor, GitHub Copilot, and more.

Your AI tool is capable. It just does not know Cypress the way you do. The toolkit fixes that with skills, context, and guidance built by the team that built Cypress.

Cypress also ships AI capabilities in the App and Cypress Cloud - such as cy.prompt(), Studio AI, Cloud MCP, Test Intent and Error Summaries, and UI Coverage test generation. Learn more in the Cypress AI documentation.

The problem this solves

AI tools can work with Cypress. What they struggle with is applying it consistently and correctly.

Without guidance, AI tools fall back on generic patterns — underusing the Cypress API, misapplying selectors, skipping best practices that experienced Cypress developers internalize over time. The result is output that technically runs but that you can't rely on.

The Cypress AI Toolkit gives your AI tools the Cypress-specific context they need to produce output you can actually build on — consistently, across your team and your workflows.

What's in the toolkit

Model Context Protocol (MCP)

The Cypress Cloud MCP server connects your AI coding assistants directly to Cypress Cloud, giving them access to data regarding your application's health and stability.

More information about the Cypress Cloud MCP is available here.

Use the first-class installer for your agent when one exists:

ToolWhen to use
Cypress Claude ConnectorFor Claude Desktop app users
Cypress Cursor PluginFor Cursor users
Cypress VS Code Extension (Cypress-io.vscode-cypress-cloud-mcp)For VS Code and GitHub Copilot users

Note: The MCP connection will utilize OAuth by default. If you would prefer to use a Personal Access Token (PAT) you will need to adjust the .mcp.json file for your agent.

Skills

Skills are instruction sets your AI tool loads to apply Cypress-specific knowledge when generating or reviewing test code. They fill the gap between what an AI learned during training and what current, well-written Cypress tests actually look like.

Five skills are available now:

  • cypress-author — Improves how AI tools create, update, and fix Cypress tests. Use it when you're writing new tests or fixing broken ones.
  • cypress-explain — Helps you understand, describe, and critique existing tests. Use it when auditing a suite, onboarding a new team member, or investigating a brittle test before rewriting it.
  • cypress-docs - Helps your agent research and retrieve information about Cypress more efficiently and reliably.
  • cypress-tap — Drives a running Cypress open-mode session to run specs, inspect results, diagnose failures, and query the app under test without GUI interaction.
  • cypress-cloud-cli — Investigates Cypress Cloud runs, tests, failures, screenshots, and Test Replay data through the Cypress Cloud CLI.

Skills work with any AI tool that accepts custom instructions, including Claude, Cursor, and GitHub Copilot.

See the skills documentation for installation instructions, example prompts, and troubleshooting.

What's coming

We're building toward a broader toolkit.

The community will help shape what gets prioritized. If you're already unlocking AI-powered Cypress workflows, we want to hear how. Open an issue or open a PR.

Getting started

Plugin

The Cypress AI toolkit is published as a plugin for installation into your agent. This is the easiest way to install and configure the various capabilities in this package and also enables an auto-update capability.

Note: Our listing in the Cursor official plugin marketplace is currently pending. This README will be updated once it is available. Until then, this repository can be cloned and installed as a local plugin in your agent of choice.

Claude

The plugin is published in the Claude Community Plugins marketplace - see the the instructions here for configuring your Claude instance to use this marketplace. Once the marketplace is configured you can search for the cypress plugin.

Manual Installation

If you're using another agent or prefer to pick-and-choose you can pick the portions of this repository you want.

  1. Install the skills using command-line tools

  • skills package:

    sh
    npx skills add cypress-io/ai-toolkit

  • GitHub CLI:

    sh
    gh skill install cypress-io/ai-toolkit

  1. Prompt your AI tool as you normally would. The skills will activate automatically when relevant, or invoke one directly with a slash command (e.g. /cypress-author).

    For manual installation, example prompts, and more, see the skills documentation or the Cypress AI Skills docs.

  2. Connect Cypress Cloud MCP with the installer for your agent (see the MCP table above). You can also copy the configuration from mcp/ or follow the configuration instructions here.

Who this is for

This toolkit is for Cypress developers who use AI coding tools and want consistent, reliable output — not just code that runs.

It's the right fit if you want your AI tool to:

  • Follow Cypress conventions and best practices without being told every time
  • Produce workflows you can repeat and build on, not just one-off completions
  • Behave consistently across your team, regardless of who's prompting

You do not need AI expertise to use it. You need Cypress and an AI coding tool.

Contributing

We welcome contributions of all kinds: new skills, improvements to existing ones, bug reports, and ideas.

If you've built something that makes AI tools smarter about Cypress, this is the right place to share it.

Read the contributing guide to get started.

Releases

PR Checks

Any change to a skill should have a corresponding semver update to the version frontmatter field in the SKILL.md file.

Changes to any functional toolkit content (skills and mcp, not documentation for example) should update the version metadata under .cursor-plugin and .claude-plugin so that plugin marketplaces can see and update accordingly.

Post-PR Actions

After an update with skill changes is merged run gh skill publish from the main branch. Preview changes with --dry-run. Version to match the plugin version above - this likely will not match the version of individual skills, but should be thought of as a "package" version.

License

MIT

Source: README.md at commit 93212fc

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Cypress integrations

Cypress Mcp

Published by GitHub account miroslavmyrha

Lets an AI assistant inspect the last Cypress test run: command log, errors, screenshots, and the DOM of failed tests.

STDIODesktop only
Developer ToolsNot validated yetOct 24, 2026