To connect an AI assistant to Cypress test runs, enable Cypress Cloud MCP for your organization, authenticate your Cypress Cloud user, then configure your AI client to connect to https://mcp.cypress.io/mcp. The integration lets a compatible assistant query recorded Cypress Cloud runs; it does not give the assistant control of a live local browser session.
What Cypress Cloud MCP connects—and what it does not
Cypress Cloud MCP connects a compatible AI coding assistant to test-run information recorded in Cypress Cloud. An assistant can help investigate CI failures, summarize run results, and query other available run data. Cypress announced general availability on May 20, 2026, and says it is included at no additional cost on all Cypress Cloud plans, including Starter. Cypress’s general-availability announcement
As an Amazon Associate I earn from qualifying purchases.
This is different from connecting an agent to a live Cypress session running on your machine. Cloud MCP queries recorded Cloud data. For local, live-session context, Cypress documents cypress tap and a Chrome DevTools MCP approach. Cypress tap documentation · Cypress live-session article
What you need before setup
- A Cypress Cloud organization and permission for an organization administrator to manage its integrations.
- A Cypress Cloud user account with access to the projects and run data you want the assistant to query.
- An AI client that supports remote MCP over HTTP and a way to authenticate it using Cypress OAuth or, if necessary, a personal access token.
Cypress says no minimum Cypress App version is required. What data the assistant can retrieve depends on your user permissions, the organization’s recorded data and retention limits, and any Cypress product subscriptions associated with particular data. Cypress Cloud MCP documentation
Connect your AI assistant to Cypress Cloud MCP
- Enable the integration for the organization. A Cypress Cloud organization administrator opens the organization’s Integrations page and enables Cloud MCP. Users cannot complete this organization-level step on their own unless they have the necessary administrator access.
- Authenticate your Cypress Cloud account. Use OAuth when your client supports it; Cypress recommends this browser sign-in flow. A personal access token (PAT) is an alternative for clients that require token-based authentication. Create the PAT from your Cypress Cloud profile and enter it only in the client’s designated secure authentication field. Cypress says a PAT is shown only once and its access follows the user’s role and permissions. Store it as a secret, not in shared configuration or source control.
- Configure the client’s remote MCP connection. Set the remote server URL to
https://mcp.cypress.io/mcp. Use Cypress’s instructions for your specific client—Cypress documents Cursor, GitHub Copilot in VS Code, GitHub Copilot CLI, and Codex CLI, and the configuration format and authentication flow differ by client. For another MCP client, verify that it supports remote MCP over HTTP and follow that client’s configuration and authentication instructions. Cypress’s client-specific setup instructions - Reconnect and confirm the tools loaded. Follow the client’s steps to restart, reconnect, or authenticate. Then check that the Cypress MCP tools appear in that client. The confirmation method is client-specific: Cypress documents
/mcpfor Copilot CLI and a new-session check for Codex; neither is a universal command.
What the assistant can investigate
Cypress documents tools for discovering projects and looking up runs. Depending on the run and the data available to your organization, a run summary can include its number, status, URL, tags, test status counts, commit author, duration, and CI build ID. Cypress also describes access to failure details, stack traces, and Test Replay links. Since general availability, Cypress says UI Coverage and accessibility data can also be queried when the relevant underlying product data is available. Cypress Cloud MCP tools and data · General-availability details
Try focused prompts that identify the run or question clearly:
- “Find the latest run on branch
mainand summarize its status and failures.” - “For the latest CI run, list failed tests with their error details and stack traces.”
- “Which tests appear flaky in the most recent run? Explain what run data supports that.”
- “Summarize the available UI Coverage and accessibility findings for this run.”
These prompts ask the assistant to interpret available recorded data. They do not mean that MCP independently changes your code, repairs tests, or proves a suspected root cause without supporting evidence.
Permissions, privacy, and request limits
- Read-only access: Cypress describes Cloud MCP as read-only. It retrieves data; it cannot edit test code or delete runs.
- User-scoped visibility: The authenticated Cypress Cloud user determines which projects and run data are visible to the assistant.
- Conversation privacy: Cypress says it receives inputs to MCP tool calls, not the AI assistant’s full chat history or context, and that returned data is not used to train or improve an LLM. Cypress security and privacy documentation
- Rate limit: Cypress’s 2026 documentation lists 100 tool requests per hour for all plans. Treat this as the documented current limit and verify it in the live documentation if your workflow depends on a specific quota.
- Retention: MCP can only query data that remains available under your organization’s Cypress Cloud recording and retention limits.
Cloud MCP versus a live local Cypress connection
| What you need | Connection | What it provides |
|---|---|---|
| Investigate recorded CI runs and historical results | Cypress Cloud MCP | Cloud run summaries, failure details, and product-dependent data such as accessibility and UI Coverage. |
| Give an agent context from a local Cypress session | cypress tap |
Cypress describes this CLI as a way for an agent to engage with a live local session. Documentation |
| Inspect the local browser, runner, DOM, or application state | Chrome DevTools MCP with Cypress | Cypress’s live-session article describes this local approach and distinguishes it from Cloud MCP’s historical run data. Article |
Troubleshooting connection and query problems
- The Cypress tools do not appear in the client. Confirm that an organization administrator enabled Cloud MCP, that the server address is exactly
https://mcp.cypress.io/mcp, and that the client supports remote MCP over HTTP. Apply that client’s restart or reconnect instructions. - OAuth does not complete or the client remains unauthenticated. Re-run the client’s Cypress sign-in flow in a browser and confirm you signed into the intended Cypress Cloud account. Check that the organization integration is enabled.
- A PAT is rejected. Confirm that the client expects a PAT rather than OAuth, that you copied the token correctly, and that the token belongs to a user with access to the target project. Because Cypress displays a PAT only once, create a replacement from your profile if the original was lost; update the client’s stored secret.
- The assistant cannot find a project, run, or expected details. Check that the authenticated user can see the project in Cypress Cloud, that the run was recorded and is still within the organization’s retention limits, and that the requested detail is available under the organization’s plan or product subscriptions.
- Requests stop succeeding during heavy use. Cypress documents a limit of 100 tool requests per hour for all plans. Reduce repeated queries and verify the current limit in the documentation before designing a high-volume workflow.
- You need the current browser or DOM state, not a past run. Cloud MCP is for recorded Cloud data. Use Cypress’s local-session options, such as
cypress tapor the documented Chrome DevTools MCP approach, for live local context.
Or skip the browser setup
For website screenshots—not Cypress test-run investigation—ScreenshotNeo offers a one-request screenshot API. It removes cookie and consent banners, newsletter popups, and chat widgets before capture; bot checks, blank pages, and failed loads are not billed; and its MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card, and paid plans start at $5 for 3,000. See the ScreenshotNeo API documentation.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
Sign up for ScreenshotNeo’s free plan: 1,000 screenshots a month, no card required.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →
