How to Use the Cypress Cloud MCP in Cursor

Q: Can Cursor automatically fix a failing Cypress Cloud spec?

Yes, Cursor uses getinstance to grab the exact error messages and screenshots from the failing spec. The agent then matches this error data with your local source files to write a targeted fix.

Q: How do I find my project ID inside Cursor?

You can ask Cursor to call listprojects to return all your project names and IDs. The editor uses this information to target the correct Cypress Cloud project for your active workspace.

Fix broken Cypress Cloud tests and refactor flaky specs directly inside Cursor using live run context.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Cypress Cloud MCP to Cursor

Create your Vinkius account to connect Cypress Cloud to Cursor and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Cypress Cloud with Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Fix broken specs using live Cursor context

The `get_instance` tool fetches live failure details from Cypress Cloud directly into your Cursor editor. You get the exact spec name, error messages, and browser info alongside the code you are currently editing. When you run Cursor in Agent mode, it reads these errors and proposes code fixes in real-time. The agent uses `get_tests` to see the exact state and duration of each individual test inside that failing spec file.

Clean up flaky code in Cursor

The `report_flaky` tool pulls your project's flaky test metrics directly into the Cursor chat panel. This lets you identify which tests pass and fail intermittently without leaving your workspace. Your Cursor agent reads the flake rates and last flake dates to locate the problematic source files. It then suggests fixes to your setup or assertions to make your test runs reliable again.

Audit test suite performance with this MCP Server

The `report_slow` tool identifies your slowest test files by sending average, p95, and maximum durations directly to your Cursor agent. This highlights the exact files that are slowing down your pull request feedback loops. By pairing this MCP Server with Cursor, you can ask the editor to analyze these slow test files and refactor them. It uses `get_runs` to monitor if your changes successfully drop overall run times on subsequent commits.

Setup guide

Set up Cypress Cloud MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the Cypress Cloud MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent Cypress Cloud transactions." If the MCP tools are loaded correctly, Cursor will call the Cypress Cloud tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

{
  "mcpServers": {
    "cypress-cloud-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Cypress. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Cypress Cloud now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Cypress Cloud MCP in Cursor

Add the MCP Server configuration to your project-level .cursor/mcp.json file. Once added, toggle Cursor Chat to Agent mode to allow the editor to call the testing tools.

Yes, Cursor uses `get_instance` to grab the exact error messages and screenshots from the failing spec. The agent then matches this error data with your local source files to write a targeted fix.

Yes, this MCP Server works with Cursor's Agent mode to run tools like `get_runs` and `report_tests`. The agent can pull down test results and update your local test files in a single pass.

You can ask Cursor to call `list_projects` to return all your project names and IDs. The editor uses this information to target the correct Cypress Cloud project for your active workspace.

Your Cypress Cloud API token is stored locally in your Cursor configuration and never exposed. Only raw test metadata, such as spec names and error traces, are fetched to help Cursor diagnose your local test files.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript