Can AI agents automate Cypress Cloud?

Cypress Cloud is automatable today through a first-party hosted MCP server. This record is the hosted Cypress Cloud test-results platform and its Cloud MCP and Cloud CLI. It is not the local Cypress runner, Playwright, or BrowserStack. Cloud MCP at https://mcp.cypress.io/mcp reached general availability on 2026-05-20 and is included on every Cypress Cloud plan. An organization admin must enable the integration. Users authenticate with OAuth (recommended, 30-day session) or a personal access token sent as Authorization Bearer. Documented tools query projects, runs, failed tests, flaky tests, Test Replay links, and plan-gated Accessibility and UI Coverage reports. The server is read-only and cannot modify test code or delete runs. Current limits are 100 tool requests per hour. The official Cloud CLI is cy-cloud (npm package @cypress/cloud). It returns JSON, authenticates with OAuth or CYPRESS_CLOUD_TOKEN, and also requires org-admin enablement. The public Cloud HTTP API opened in this pass is the Enterprise Data Extract API at https://cloud.cypress.io/enterprise-reporting/report. It authenticates with an organization API key as a token query parameter, is Enterprise-plan-only, and returns read-only reporting in csv, json, or xlsx. Outbound webhooks POST run.completed JSON; vendor docs mark webhooks as early access on paid plans and trials. iPaaS connectors were not opened. Computer-use viability is unassessed. MCP and CLI both score 7; MCP is the best path because it is the hosted agent contract and does not require a local CLI install.

Best path today: mcp · Overall automatability: 7/10