Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
Cypress Cloud MCP
Overview
Description from the maker (original English)
Direct access to Cypress tests results and accessibility reports in your AI workflow.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs in the cloud
- Transport: Streamable HTTP
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on the maker’s server: what you ask it goes through their server.
- The registry lists no key to fill in.
You need
- Runs in the cloudNothing to install; it connects over the internet
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
- Open Settings → Connectors
- Press Add custom connector
- Paste the address below and press Add
- If it asks you to sign in, sign in with the maker
https://mcp.cypress.io/mcpRun this in your terminal
claude mcp add --transport http cypress-cloud https://mcp.cypress.io/mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"cypress-cloud": {
"url": "https://mcp.cypress.io/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"cypress-cloud": {
"type": "http",
"url": "https://mcp.cypress.io/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
- Open ChatGPT on the web → Settings → Connectors (Apps)
- Press Create or Add (some plans need Developer mode under Advanced first)
- Paste the address below, give it a name and save
- If it asks you to sign in, sign in with the maker
https://mcp.cypress.io/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
We have not read this server’s tool list yet; we check endpoints in rotation.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified against the domain mcp.cypress.io (the registry checks domain ownership)
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- … Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
- … Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
- … Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint
Compared with others in Otheri
- More stars than 0% of the other 32545 servers in this category
- Published to the registry more recently than 10% of the other 32545 servers in this category
- Basic checks equal to or better than 100% of the other 32545 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Cypress Cloud MCP safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
Is it still maintained?
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 5 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, Python MCP
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated yesterday
Install
Python MCP
by Files-com
Local-only Python MCP server for the Files.com API.
Runs on your computerUpdated today
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
✨ 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`](./skills/README.md#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`](./skills/README.md#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`](./skills/README.md#cypress-docs) - Helps your agent research and retrieve information about Cypress more efficiently and reliably.
- [`cypress-tap`](./skills/README.md#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`](./skills/README.md#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-toolkitGitHub CLI:sh 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.
License
MIT