
Playrunner.dev
From $30/moActively maintained
- Is it safe? We have not read the data policy of Playrunner.dev yet. Read it on the official site before you upload anything.playrunner.dev ↗
- Is it free? From $30/mo · pricing page, read Oct 26, 2026See ↓
- What else does this? We have not measured alternatives for this one yet. If you know one, add it below.See ↓
not read yet
Use
- For
- Developers using AI coding agents on apps where payments, bookings and customer journeys must keep working
- Price
- From $30/mopricing page, read Oct 26, 2026
- Activity
- Actively maintainedrelease 11 days ago · site updated 11 days ago
- How it runs
- CLI
- Used for
- Run saved Playwright tests in the background
- Check agent-made code changes against existing customer journeys
- Review test results and artifacts after failed runs
- Has an MCP server (1 in the registry)public registry →
- Publishes llms.txt, a file written for AI assistantsplayrunner.dev ↗
- MCP serverdev.playrunner/mcpverified in the MCP registry
- Stateanswers, requires sign-inchecked 2026-10-26
- Address to connectplayrunner.cloud/mcp
This card as JSON, for your agent →
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Not it? Say what you need
betaThree tools from the Atlas for the job you describe, each with what fits and what does not.
No notes yet. What do you use Playrunner.dev for?
Sign in to leave a noteWhat is Playrunner.dev?
Runs saved Playwright browser tests and returns failing steps, expected results and captured evidence to your AI agent.
Who is Playrunner.dev for?
Developers using AI coding agents on apps where payments, bookings and customer journeys must keep working
How much does Playrunner.dev cost?
Paid plans start at $30/mo, per Playrunner.dev's pricing page on 2026-10-26.
Do people use Playrunner.dev?
Little sign of use.
Is Playrunner.dev still maintained?
Actively maintained: release 11 days ago · site updated 11 days ago.
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.
How we read every tool → · By INITE Atlas Desk
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.