For coding agents
Works where your agent works.
Claude Code, Cursor and Codex write a lot of the code now. Smoke Run tests that work the way a customer meets it, then hands the result back to the agent so it can fix what broke.
On every pull request
Every push your host deploys, preview or live, is tested in a real browser. The result lands on the pull request as a comment and on the commit as a commit status named Smoke Run, so Claude Code, Cursor or Codex can read it and fix what broke. Make that status a required check in your branch protection and a failing run blocks the merge.
- 01
Sign in and open QA on every push on your dashboard. Sign in
- 02
Enter your repository, then add the webhook it shows you in the repository settings on GitHub, with the Deployment statuses and Statuses events.
- 03
Paste a fine-grained token for that repository with Commit statuses, Pull requests and Contents set to read and write. Smoke Run uses it to post the comment and the status.
- 04
On Vercel, turn on deployment_status events under Project Settings, Git, so every preview gets tested too.
- 05
To block a merge on a failing run, add Smoke Run as a required status check in your branch protection rule.
Inside your agent
Add the Smoke Run MCP server and your agent can call run_revenue_check on a site before it calls the job done. The first 5 checks a day need no key and no account. Every finding comes back with a confidence label, so the agent knows what was proven and what was only seen.
- 01
In Claude Code, run this once.
claude mcp add --transport http smoke-run https://getsmokerun.com/api/mcp - 02
In Cursor or any other MCP client, add the server address to its MCP config.
{ "mcpServers": { "smoke-run": { "url": "https://getsmokerun.com/api/mcp" } } } - 03
Ask your agent to run run_revenue_check on your site after each deploy. The first 5 checks a day need no key.
- 04
For more checks, buy run credits or Agent Unlimited on the developers page. Buy runs
The history stays with you
Every push run lands on your dashboard with its verdict and a recording of what the test user saw, next to your site crawls. You can see what broke since the run before and when each flow was last verified.
- 01
Each push run shows its verdict, the pages it judged affected, the screenshots and the recording.
- 02
Each flow shows when it was last verified and when it is next due.
- 03
Each crawl is compared with the one before, so you see what broke, what got fixed and which pages are new or gone.
Checks on every push come with every account. Past the free MCP checks, run credits or Agent Unlimited cover the volume. Solo and Pro add the scheduled whole-site crawl and the Watch on your money path. Compare plans
Run a free teardown