Changelog

Findings in your editor, over MCP

  • New

Claude Code, Cursor and any MCP client can now read your organization's runs, checks and findings, so your coding agent fixes what the browser saw without you pasting the report.

Your coding agent can now read ZeusQA directly. Add the ZeusQA MCP server once and ask it things like "what failed on the last checkout run, and how do I fix it?".

  • Three read-only tools. list_runs gives the newest runs with their verdicts. get_run gives one run's summary, checks and QA and security finding counts. get_findings gives what the browser found, most severe first, each marked QA or security, with the evidence and a suggested fix.
  • Organization API tokens. Owners and admins create a named token in Connections, MCP. The token is shown once and only a hash of it is stored. Revoke it and the next call gets a 401.
  • Copy and paste setup. The MCP page has the endpoint, a claude mcp add command and a .cursor/mcp.json block, with your new token already in them.
  • Read-only. Nothing the agent calls can start, stop or change a run. It sees only runs from the organization the token belongs to.

MCP is on every plan. Open Connections to set it up.

Part of the ZeusQA changelog. Follow new releases with the RSS feed.

Try it on your own site

Paste a URL, describe the flow in plain English, and watch a real browser do it. Three runs free, no card.