2,500+ MCP servers ready to use
Vinkius

Cypress Cloud MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Cypress Cloud and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "cypress-cloud": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Cypress Cloud
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Cypress Cloud MCP Server

Connect your Cypress Cloud enterprise account to any AI agent and take full control of your end-to-end testing lifecycle and quality metrics through natural conversation.

GitHub Copilot Agent mode brings Cypress Cloud data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

  • Run Monitoring — List recent test executions for your projects and retrieve detailed passed/failed/pending counts and commit info
  • Instance Deep Dives — Inspect specific spec file executions to retrieve error messages, screenshots, and video URLs for failed tests
  • Flaky Test Identification — Generate enterprise reports to identify intermittent failures and audit last flake dates across your codebase
  • Performance Auditing — Retrieve slow test reports to evaluate average durations and p95 performance metrics for your CI/CD pipeline
  • Enterprise Reporting — Fetch aggregated run summaries and granular test result data formatted for BI dashboards and audits
  • Project Navigation — List all organizational projects and identify unique 6-character IDs required for programmatic data extraction

The Cypress Cloud MCP Server exposes 10 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Cypress Cloud to VS Code Copilot via MCP

Follow these steps to integrate the Cypress Cloud MCP Server with VS Code Copilot.

01

Create MCP config

Create a .vscode/mcp.json file in your project root

02

Add the server config

Paste the JSON configuration above

03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

04

Start using Cypress Cloud

Ask Copilot: "Using Cypress Cloud, help me...". 10 tools available

Why Use VS Code Copilot with the Cypress Cloud MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Cypress Cloud through the Model Context Protocol.

01

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Cypress Cloud + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Cypress Cloud MCP Server delivers measurable value.

01

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

02

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

03

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

04

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Cypress Cloud MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect Cypress Cloud to VS Code Copilot via MCP:

01

get_instance

Get full details of a Cypress spec instance including spec name, status, error messages, screenshots, video URLs, and browser info

02

get_instances

List spec instances within a Cypress run. Each instance represents one spec file execution. Returns instance IDs, spec names, statuses, and durations

03

get_run

Get full details of a Cypress Cloud run including status, total tests, passed/failed/pending counts, duration, parallelization, groups, and commit info

04

get_runs

List recent test runs for a Cypress Cloud project. Returns run IDs, commit info, branch, CI build IDs, statuses (passed/failed/running), durations, and spec counts

05

get_tests

List individual tests within a Cypress spec instance. Returns test titles, states (passed/failed/pending/skipped), durations, and error messages

06

list_projects

Useful for finding the `project_id`. List all projects on Cypress Cloud. Cypress is the leading JavaScript E2E testing framework. Returns project names, IDs, and org info via the Enterprise Data Extract API

07

report_flaky

Get flaky test report from Cypress Cloud. Identifies tests that intermittently pass/fail. Returns test names, flake rates, and last flake dates

08

report_runs

Must provide the start date. Get enterprise run summary report from Cypress Cloud. Aggregated data for BI dashboards. Requires start_date (YYYY-MM-DD)

09

report_slow

Get slow test report from Cypress Cloud. Identifies slowest tests by average duration. Returns test names, avg/p95/max durations

10

report_tests

Get enterprise test results report from Cypress Cloud. Individual test-level data with statuses and error messages

Example Prompts for Cypress Cloud in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Cypress Cloud immediately.

01

"List the last 5 test runs for project 'abc123'"

02

"Show me why instance 'ins_789' failed"

03

"Give me a report of flaky tests starting from 2024-01-01"

Troubleshooting Cypress Cloud MCP Server with VS Code Copilot

Common issues when connecting Cypress Cloud to VS Code Copilot through the Vinkius, and how to resolve them.

01

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Cypress Cloud + VS Code Copilot FAQ

Common questions about integrating Cypress Cloud MCP Server with VS Code Copilot.

01

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
02

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
03

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
04

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.

Connect Cypress Cloud to VS Code Copilot

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.