dev.playrunner/mcp is an MCP server that discover Playwright workflows, start runs, and inspect results in Playrunner Cloud. Its tool list has not been published yet over http, requires no API key, and scores 55/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"dev-playrunner-mcp": {
"args": [
"-y",
"playrunner"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Discover Playwright workflows, start runs, and inspect results in Playrunner Cloud.
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked playrunner against OSV.dev.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in browser
Open-source web scraper for AI agents with scrape, crawl, and map tools
Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡
Search-first MCP server for JavaScript reverse engineering: 735 tools across 36 domains.
Firecrawl, the context API for AI agents: search, scrape, interact with the web, plus paper search.
MCP Security Weekly
Get CVE alerts and security updates for dev.playrunner/mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Playrunner turns your Playwright tests into reusable workflows
your team, your CI, and your coding agent can run.
Go from “the code is done” to “here is what passed”.
Run real browser checks. Follow the execution. Open the report, trace, or video.
Try Playrunner Cloud → · Run locally · Connect your agent · Read the docs
Recorded with OBS and narrated with AI on 19 October 2026. The overview shows product examples; the workflow video tours a real local run’s saved configuration, passing report, and screenshot evidence. Video notes and transcripts →
A working-looking screen is a good start. A repeatable test with an inspectable result is something your team can build on.
Playrunner gives AI-assisted developers and test teams a shared place to run Playwright, reuse environments and browser sign-ins, and investigate failures. Keep your existing tests. Give them a workflow you can run again after the next change.
Connect a compatible MCP client to Playrunner Cloud, then ask:
Run my checkout smoke workflow once. Wait for it to finish, tell me which tests passed or failed, and include the report links.
The agent can discover projects, create workflows, start runs, and inspect the returned evidence from the same conversation. Your saved workflows remain available to your teammates and CI.
Codex · Claude · Cursor · Gemini CLI · Antigravity · Grok
Connection steps and capabilities vary by client. Use a client with remote Streamable HTTP and OAuth support, or the CLI from a shell-capable agent. [Choose your connection →](htt