How to Use the Cypress Cloud MCP in VS Code Copilot

Q: Can VS Code Copilot analyze flaky tests from Cypress Cloud?

Yes, VS Code Copilot uses the reportflaky tool to fetch flake rates and dates. This helps your team quickly identify which tests are causing intermittent build failures in your deployment pipeline.

Q: How do I run enterprise reports with Cypress Cloud in VS Code Copilot?

You can ask VS Code Copilot to run reportruns by providing a start date. The server pulls down the aggregated metrics, allowing Copilot to summarize team performance directly in your chat panel.

Q: How does this server map my VS Code workspace to the correct project?

The MCP Server reads this list of projects via listprojects to map your active workspace folder to the correct Cypress Cloud project ID. This prevents you from running queries against the wrong testing environment.

Share Cypress Cloud test diagnostics and flaky reports across your entire team inside VS Code Copilot.

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 VS Code Copilot

Create your Vinkius account to connect Cypress Cloud to VS Code Copilot 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 VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Debug team-wide failures with VS Code Copilot

The `get_run` tool pulls complete Cypress Cloud run statuses, including passed, failed, and pending counts, directly into VS Code Copilot. This gives your team instant visibility into CI build failures without leaving the editor. Developers can use `get_instances` to list every spec execution within a broken run. VS Code Copilot reads the instance IDs and durations to help you divide and conquer broken test suites during active sprints.

Track enterprise test metrics in VS Code Copilot

The `report_runs` tool pulls aggregated run summary data into VS Code Copilot for specific date ranges. This allows engineering leads to review overall suite health and commit-level success rates directly from chat. You can also use `report_tests` to pull raw test-level data, including error messages and execution statuses. VS Code Copilot processes this data to help you spot recurring issues across your entire codebase.

Eliminate flaky tests using this MCP Server

The `report_flaky` tool exposes intermittent test failures to VS Code Copilot, detailing exactly which tests are breaking your CI pipelines. Your team can run this tool to generate a prioritized list of tests that need refactoring. By committing this MCP Server configuration to your repository, every developer on the team gets access to these diagnostics. VS Code Copilot uses `report_slow` to ensure everyone can quickly identify and optimize the slowest specs in the suite.

Setup guide

Set up Cypress Cloud MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the Cypress Cloud MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the Cypress Cloud tools listed. Try asking: "List my recent Cypress Cloud transactions" and Copilot will invoke them automatically.

.vscode/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 VS Code Copilot

Create a .vscode/mcp.json file in your project root and commit it to Git. Once your team members update to VS Code 1.96+, Copilot Chat will automatically detect the Cypress Cloud MCP Server.

Yes, VS Code Copilot uses the `report_flaky` tool to fetch flake rates and dates. This helps your team quickly identify which tests are causing intermittent build failures in your deployment pipeline.

You can ask VS Code Copilot to run `report_runs` by providing a start date. The server pulls down the aggregated metrics, allowing Copilot to summarize team performance directly in your chat panel.

The MCP Server reads this list of projects via `list_projects` to map your active workspace folder to the correct Cypress Cloud project ID. This prevents you from running queries against the wrong testing environment.

Your Cypress Cloud test results and run history are routed directly through your local VS Code environment. No test metadata, spec names, or performance reports are stored on external servers outside your secure enterprise configuration.

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