Run audits from your tools.
Issue a key, then start an audit from Claude Code, curl or the qa-swarm CLI. Every surface uses the same key and the same wallet.
Keys for your organization.
Use a key for the remote MCP server, the JSON API, the CLI and CI. The full key shows once, when you create it.
Sign in to create a key. With one key you connect Claude Code, the JSON API or the CLI.
Connect a client.
Create a key to fill it in.
Claude Code
Run this one command in your terminal to register the Excuto MCP server in Claude Code. Cursor and Codex snippets follow after we test them in those clients.
claude mcp add --transport http qa-swarm https://us-central1-xenon-qa.cloudfunctions.net/api/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
Sites you own.
A passive audit works on any public URL. For the active audit, prove you own the site with a DNS TXT record (_qa-verify). The active audit also clicks, types bad input and double-clicks.
A GitHub check on every pull request is not built yet.
What the MCP server gives your agent.
Four tools. Each one checks the scope of your key.
- run_cloud_qa_audit
- Starts an audit of a URL and returns the job id at once.
- audits:write
- get_qa_job_status
- Gives the status, the latest progress lines and the number of findings in review.
- audits:read
- get_verified_bugs
- Gives the findings a person approved: steps, root cause and a Playwright test. Findings in review appear only as a count.
- audits:read
- get_audit_report
- Gives the summary, the coverage and the link to the full report.
- audits:read