iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
To connect an AI assistant to Cypress test runs, enable Cypress Cloud MCP for your organization, authenticate your Cypress Cloud account, then configure your client to use https://mcp.cypress.io/mcp. This connects the assistant to recorded Cypress Cloud run data for investigation; it does not give the assistant control of a live local Cypress browser session.
What Cypress Cloud MCP connects to
Cypress Cloud MCP lets a compatible AI coding assistant query test runs recorded in Cypress Cloud. Depending on your permissions, available run data, plan limits, and Cypress products, the assistant can retrieve run summaries, failure details, stack traces, Test Replay links, and—in organizations with the relevant data—UI Coverage and accessibility information. Cypress announced general availability on May 20, 2026, and says the integration is included on all Cypress Cloud plans, including Starter, at no additional cost. Cypress’s general-availability announcement
This is distinct from connecting an agent to a live local test session. For live-session context, Cypress documents cypress tap; its live-session article also discusses Chrome DevTools MCP. Cypress tap documentation · Cypress live-session guide
Recommended Free Tools
Before you configure the assistant
- You need access to a Cypress Cloud organization and the projects and run data you want the assistant to inspect.
- An organization administrator must enable Cloud MCP in the organization’s Integrations page.
- Your AI client must support remote MCP over HTTP and provide a way to configure authentication.
- Cypress says there is no minimum Cypress App version requirement. The assistant can only query data available under your organization’s Cypress Cloud plan and retention limits. Cypress Cloud MCP documentation
Connect Cypress Cloud MCP step by step
- Enable the integration: In Cypress Cloud, an organization administrator opens the organization’s Integrations page and enables Cloud MCP. The exact navigation around this page may vary with the Cloud interface.
- Choose authentication: Cypress recommends OAuth, which lets you sign in through a browser. Use a personal access token (PAT) only if your client requires token-based authentication. Cypress says a PAT is created from your Cypress Cloud profile, shown only once, and limited by the user’s existing role and permissions. Store it as a secret; do not commit it to a repository or paste it into shared configuration.
- Configure the client endpoint: Add Cypress’s remote MCP server URL,
https://mcp.cypress.io/mcp, using your client’s documented setup for remote HTTP MCP. Configuration file names, OAuth flows, and token fields differ between clients, so follow the current instructions for your specific client rather than copying another client’s configuration verbatim. - Reconnect and confirm: Complete the browser sign-in or provide the PAT, then reconnect or restart the MCP connection as the client requires. Confirm that the Cypress MCP tools are available. Cypress documents
/mcpas a check in Copilot CLI and recommends checking the tools in a new session for Codex; neither check is a universal command for every client. Client-specific setup and checks
What to ask the connected assistant
Once connected, ask questions that identify the project, branch, or run you want examined. Cypress’s documented examples include queries about the latest CI run on main and flaky tests. For example:
- “Summarize the failures in the latest CI run on
main, and include the run URL.” - “Which tests failed in run 1234? Group them by likely cause and cite the available stack traces.”
- “Which tests appear flaky in the most recent run, and what evidence in the recorded results supports that?”
- “For this run, what UI Coverage or accessibility findings are available?”
The assistant is querying recorded data, not proving that it has fixed the code. Treat its root-cause analysis as a lead: verify the cited failure, stack trace, replay, or coverage finding in Cypress Cloud and your code before changing a test or application.
Permissions, privacy, and request limits
Cypress describes Cloud MCP as read-only: it retrieves data and cannot change test code or delete runs. Its access is scoped to what the authenticated Cypress Cloud user can already see. Cypress says it receives inputs to MCP tool calls, not the assistant’s full chat history or context, and says returned data is not used to train or improve an LLM. Cypress security and privacy details
Cypress’s documentation lists a limit of 100 tool requests per hour for all plans. That is a tool-request limit, not a statement about how many test runs your organization retains. Run-data availability follows the recording and retention limits of your Cypress Cloud plan. Check the current documentation if these limits affect a production workflow.
Troubleshooting connection and query problems
- The Cypress tools do not appear: Verify that an organization administrator enabled Cloud MCP, that the endpoint is exactly
https://mcp.cypress.io/mcp, and that the client supports remote MCP over HTTP. Reconnect or restart the client after completing authentication. - OAuth does not complete: Repeat the authorization flow in the client’s current Cypress setup instructions and finish the browser sign-in with the intended Cypress Cloud account. Check that the organization integration is enabled and that the account can access the target projects.
- The client requires a PAT: Create the token from your Cypress Cloud profile and configure it through the client’s supported secret or authentication mechanism. Cypress says the token is displayed once; if it was not saved, create a replacement rather than trying to recover the original. Never expose it in prompts or committed files.
- A project or run is missing: The authenticated user may not have permission to see it, the run may not have been recorded in Cloud, or the data may fall outside the organization’s plan or retention limits. Confirm the run exists in Cypress Cloud and that the user can view it there.
- Coverage or accessibility information is absent: Those results depend on the relevant Cypress product and data being available for the organization and run. A missing result does not establish that the assistant has found no issues.
- Queries stop working after repeated calls: Cypress documents a 100-tool-requests-per-hour limit across plans. Reduce repeated exploratory calls or wait for the limit window to clear.
- A client-specific verification command fails: Commands such as
/mcpare documented for particular clients, not universally. Use the client’s own Cypress connection instructions to inspect or reconnect its MCP server.
Or skip the browser setup
ScreenshotNeo is a website screenshot API, not a Cypress run-data connector, so it cannot replace Cypress Cloud MCP for querying test results. It is useful when the next step is capturing a page for visual inspection. One GET request returns a screenshot or PDF; see the ScreenshotNeo service and its API documentation.
Quick Recap
For example, capture a page as WebP with cURL:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before capture; bot checks, blank pages, and failed loads are not billed. Its MCP server lets AI agents take screenshots, and the free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. Sign up for 1,000 free screenshots a month, with no card.
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.
