Alejandro Estrada
b7e92bc221
* Create VSCode extension for MCP * Make version 1.0.0 * Add MIT license file and update package.json to include license information. Implement welcome message tracking in extension and enhance tests to verify license file existence. * Update VSCode extension name and documentation for Cypress Cloud MCP integration - Renamed the extension from `cypress-cloud-mcp-integration` to `vscode-cypress-cloud-mcp` in package.json and related files. - Enhanced README and other documentation to reflect the new extension name and provide clearer installation and usage instructions. - Added a new SVG icon for the extension and removed the old PNG icon. - Updated references to the extension in various documentation files to ensure consistency. * Update with review * Update with review * Update logo * Remove Marketplace ID from README for Cypress Cloud MCP * Update vscode-cloud-mcp/package.json Co-authored-by: Emily Wisniewski (Rohrbough) <emilyr@cypress.io> --------- Co-authored-by: Emily Wisniewski (Rohrbough) <emilyr@cypress.io>
✨ 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:
| Tool | When to use |
|---|---|
| Cypress Claude Connector | For Claude Desktop app users |
| Cypress Cursor Plugin | For 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.
- Install the skills using command-line tools
-
skillspackage:npx skills add cypress-io/ai-toolkit -
gh skill install cypress-io/ai-toolkit
-
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.
-
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.
VS Code extension changes are built, packed, and published separately. See Pack and release in the extension README.