Cloud MCP UI Coverage Tools (#6436)

emilyrohrbough · web-flow · commit fa8f60eba6ec · 2026-05-05T16:20:18.000-05:00
diff --git a/docs/cloud/features/cypress-ai-features.mdx b/docs/cloud/features/cypress-ai-features.mdx
@@ -158,7 +158,7 @@ Error Summaries are available on all Cypress Cloud plans at no additional cost.
 
 Cloud MCP is a remote server that gives AI assistants a direct window into your application’s health and stability. By connecting your AI coding assistant or AI agent directly to your CI results, it transforms Cypress from a testing tool into a real-time engineering data source—removing the manual overhead that makes testing a bottleneck.
 
-Instead of spending time investigating runs, your assistant uses the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) to independently monitor and analyze recorded run data, including errors, stack traces and test replay links. This makes it easier to reach for Cypress as your tool of choice.
+Instead of spending time investigating runs, your assistant uses the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) to independently monitor and analyze recorded run data, including errors, stack traces, test replay links, accessibility violations, and UI Coverage gaps. This makes it easier to reach for Cypress as your tool of choice.
 
 Read the [Cloud MCP documentation →](/cloud/integrations/cloud-mcp)
 
diff --git a/docs/cloud/integrations/cloud-mcp.mdx b/docs/cloud/integrations/cloud-mcp.mdx
@@ -259,16 +259,19 @@ Each time the Cloud MCP connection is established, any new tools become immediat
 
 Some tools are relevant for all Cypress Cloud plans (including free), but some others are for **plan-specific data** like flaky test reporting, or **product-specific data** like Cypress Accessibility violation details. These are only available if your organization has subscriptions for the plans and products that would provide the underlying data.
 
-| Tool                                      | Capability                                                                                                                                                         | Best Use Case                                                           |
-| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------- |
-| `cypress_get_projects`                    | Lists all projects in your Org.                                                                                                                                    | Helping the agent find the correct `projectId` for subsequent queries.  |
-| `cypress_get_runs`                        | Returns run summaries for a project, run URL, or git branch. Summaries include project name, run number, status, run URL, tags, and test status counts.            | "Check the status of the last CI run on main"                           |
-| `cypress_get_failed_test_details`         | Retrieves attempt details: test name, spec, attempt error and stack trace, and a Test Replay link for quick debugging. Does not return test artifacts.             | "Analyze why the checkout test failed in the latest run."               |
-| `cypress_get_flaky_tests`                 | Identifies the flaky tests in a run.                                                                                                                               | "Are these failures regressions or known flakiness?"                    |
-| `cypress_get_accessibility_report`        | Returns a high-level accessibility report for a run: violation counts by severity, failing rules with element counts, and the top 5 views sorted by failure count. | "Summarize accessibility violations for the latest run on this branch." |
-| `cypress_get_accessibility_views`         | Returns paginated views from an accessibility report, sorted by number of failing rules. Use to browse all views beyond the top 5 in the report summary.           | "Which pages have the most accessibility failures in this run?"         |
-| `cypress_get_accessibility_rule_failures` | Returns paginated failing DOM elements for a specific accessibility rule, with CSS selector, view, and failure message. Optionally scope to a specific view.       | "Show me all color-contrast failures on the checkout page."             |
-| `cypress_feedback`                        | Shares feedback with Cypress directly from your agentic environment.                                                                                               | "Report a bug or request a new MCP feature."                            |
+| Tool                                      | Capability                                                                                                                                                                                         | Best Use Case                                                           |
+| ----------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- |
+| `cypress_get_projects`                    | Lists all projects in your Org.                                                                                                                                                                    | Helping the agent find the correct `projectId` for subsequent queries.  |
+| `cypress_get_runs`                        | Returns run summaries for a project, run URL, or git branch. Summaries include project name, run number, status, run URL, tags, and test status counts.                                            | "Check the status of the last CI run on main"                           |
+| `cypress_get_failed_test_details`         | Retrieves attempt details: test name, spec, attempt error and stack trace, and a Test Replay link for quick debugging. Does not return test artifacts.                                             | "Analyze why the checkout test failed in the latest run."               |
+| `cypress_get_flaky_tests`                 | Identifies the flaky tests in a run.                                                                                                                                                               | "Are these failures regressions or known flakiness?"                    |
+| `cypress_get_accessibility_report`        | Returns a high-level accessibility report for a run: violation counts by severity, failing rules with element counts, and the top 5 views sorted by failure count.                                 | "Summarize accessibility violations for the latest run on this branch." |
+| `cypress_get_accessibility_views`         | Returns paginated views from an accessibility report, sorted by number of failing rules. Use to browse all views beyond the top 5 in the report summary.                                           | "Which pages have the most accessibility failures in this run?"         |
+| `cypress_get_accessibility_rule_failures` | Returns paginated failing DOM elements for a specific accessibility rule, with CSS selector, view, and failure message. Optionally scope to a specific view.                                       | "Show me all color-contrast failures on the checkout page."             |
+| `cypress_get_ui_coverage_report`          | Returns a high-level UI Coverage report for a run: overall coverage score, tested and untested element and link counts, and the top 5 riskiest views sorted by most untested interactive elements. | "Summarize UI Coverage for the latest run on this branch."              |
+| `cypress_get_ui_coverage_views`           | Returns paginated views from a UI Coverage report, sorted by most untested elements and links. Use to browse all views beyond the top 5 in the report summary.                                     | "Which pages have the most untested elements in this run?"              |
+| `cypress_get_ui_coverage_elements`        | Returns paginated interactive elements for a run. Filter by tested or untested, and optionally scope to a specific view by name.                                                                   | "Show me the untested elements on the checkout page in this run."       |
+| `cypress_feedback`                        | Shares feedback with Cypress directly from your agentic environment.                                                                                                                               | "Report a bug or request a new MCP feature."                            |
 
 ## Writing effective prompts
 
@@ -300,7 +303,11 @@ To get the most out of Cloud MCP, follow these three principles:
 
 > "Pull the Cypress Cloud Accessibility report for the latest run on this branch. List any critical or serious violations grouped by rule, and tell me which views are most impacted."
 
-For more a deeper exploration of working with Cloud MCP's accessibility tools, read our guide [Cypress Accessibility - Work with AI agents](/accessibility/work-with-ai-agents).
+For a deeper exploration of working with Cloud MCP's accessibility tools, read our guide [Cypress Accessibility - Work with AI agents](/accessibility/work-with-ai-agents).
+
+### The UI Coverage Triage
+
+> "Using Cypress Cloud, pull the UI Coverage report for the latest run on this branch. Tell me the overall coverage score, list the views with the most untested elements, and show me the specific untested elements on the riskiest view."
 
 ## FAQs
 
@@ -355,3 +362,4 @@ Alternatively, use [this feedback form](https://share.hsforms.com/2NWNpyi5KSZmG4
 - [Recording Cloud Runs](/cloud/features/recorded-runs)
 - [Cypress AI](/cloud/features/cypress-ai-features)
 - [cy.prompt()](/api/commands/prompt)
+- [Cypress Accessibility - Work with AI agents](/accessibility/work-with-ai-agents)
diff --git a/docs/ui-coverage/get-started/introduction.mdx b/docs/ui-coverage/get-started/introduction.mdx
@@ -157,5 +157,6 @@ UI Coverage provides an interactive, visual map of test coverage for your applic
 - **Flexible configuration**: Customize and fine-tune UI Coverage to suit specific needs and scenarios like ignoring views or elements or grouping similar elements together.
 - **Configurable CI Integration**: The [Results API](/ui-coverage/results-api) allows you to programmatically control your CI pipeline's behavior based on UI Coverage scores.
 - **Run-specific configuration**: Use [Profiles](/ui-coverage/configuration/profiles) to apply different configuration settings based on run tags, enabling team-specific reporting and optimized settings for different run types.
+- **AI agent integration**: Use [Cypress Cloud MCP](/cloud/integrations/cloud-mcp) to query coverage scores, identify untested views, and generate tests directly from your AI coding assistant.
 
 Read more about how it works in the [Core Concepts](/ui-coverage/core-concepts/interactivity) section.
diff --git a/docs/ui-coverage/guides/address-coverage-gaps.mdx b/docs/ui-coverage/guides/address-coverage-gaps.mdx
@@ -45,6 +45,10 @@ The generated code will use your existing patterns for navigating and interactin
 
 This test can be copied directly into your spec file at the suggested location, and from there you can continue writing the test locally.
 
+:::tip
+If you use an AI coding assistant, [Cypress Cloud MCP](/cloud/integrations/cloud-mcp) lets your agent pull UI Coverage data directly into your editor. You can ask it to identify the untested elements on a specific view and write targeted tests for them — combining Cloud data with your local code in a single workflow.
+:::
+
 ### Write tests for specific elements
 
 Focus on creating tests that interact with the specific untested elements or pages identified in the coverage reports. For example:
diff --git a/docs/ui-coverage/guides/identify-coverage-gaps.mdx b/docs/ui-coverage/guides/identify-coverage-gaps.mdx
@@ -38,6 +38,10 @@ describe('UI Coverage Scan', () => {
 
 Once your tests have recorded to Cypress Cloud, you can analyze the coverage reports to identify gaps. Click on the runs in your project in [Cypress Cloud](https://on.cypress.io/cloud) to access the UI Coverage reports. This report provides a visual representation of your application's test coverage, highlighting tested and untested elements.
 
+:::tip
+If you use an AI coding assistant, you can query UI Coverage data directly from your editor using [Cypress Cloud MCP](/cloud/integrations/cloud-mcp). Ask your agent to pull the report, identify the riskiest views, and drill into specific untested elements — without opening a browser tab.
+:::
+
 ### Overall Score
 
 The first metric to review is the **overall coverage score**. This score is calculated by comparing the number of tested elements to the total number of [interactive elements](/ui-coverage/core-concepts/interactivity) in your application. A higher score indicates better coverage, while a lower score indicates areas that need additional testing. The score will display on the runs page and within individual runs.
