Browser Use
Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.
Discover Playwright workflows, start runs, and inspect results in Playrunner Cloud.
Pick the AI app you use, then copy the settings.
Passed 4/5 checks · What you ask goes through the maker’s server (playrunner.cloud) · ✓ Commands checked Nov 13, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude · about 2 min
No key, nothing to install · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it
CustomizeConnectors
Copy each value into the field with the same name in Claude, then click Continue
Playrunnerhttps://playrunner.cloud/mcpClick Continue past the sign-in settings Claude detected · under Authentication choose what the maker says (Sign in now, Sign in when needed or No sign in), then click Add
+ConnectorsPlayrunner
Use Playrunner and tell me what you can do for me, then show me one thing✓ If Claude says it is using Playrunner or shows a Playrunner tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with ChatGPT, depending on your plan
Full MCP: ChatGPT Business, Enterprise or Edu on the web · Pro: connects with read/fetch permissions, so tools that change data may not work · Plus: not confirmed in OpenAI’s docs; if you see an add-custom-MCP option on the Plugins page you can try these steps · web only
Plugins+Add custom MCP server
Enter a name, paste the address under Connection, tick the risk warning and click Create as a plugin
Playrunnerhttps://playrunner.cloud/mcpStart a new chat and pick Playrunner from your plugins before typing
Use Playrunner and tell me what you can do for me, then show me one thing✓ If ChatGPT says it is using Playrunner or shows a Playrunner tool in the answer, you are connected
Menu names checked against OpenAI’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Claude Code · about 2 min
No key, nothing to install
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --transport http --scope user playrunner https://playrunner.cloud/mcpYou should see Playrunner listed as connected
Use Playrunner and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Playrunner or shows a Playrunner tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor · about 2 min
No key, nothing to install
Use Playrunner and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Playrunner or shows a Playrunner tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code · about 2 min
No key, nothing to install
Use Playrunner and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Playrunner or shows a Playrunner tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
Address for apps that connect over the web
https://playrunner.cloud/mcpJSON settings are under “For developers” below
Claude Code
claude mcp add --transport http --scope user playrunner https://playrunner.cloud/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"playrunner": {
"url": "https://playrunner.cloud/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"playrunner": {
"type": "http",
"url": "https://playrunner.cloud/mcp"
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Connect over the internet in
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
The server asks you to sign in before it lists its tools.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 14, 2026
The registry name was verified against the domain playrunner.dev (the registry checks domain ownership)
Code last changed 2 days ago
GitHub could not identify the licence type; open the file to check
Responded in 1166 ms (HTTP 401)
Declares OAuth sign-in, so your AI app can take you to log in
Not checked yet; we read the tool list when we check the endpoint
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 4 of 5 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed 2 days ago, and the latest version (0.1.1) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).
In the same category: Browser Use, Scrapling MCP Server, Chrome DevTools MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.
Web scraping with stealth HTTP, real browsers, and Cloudflare bypass. CSS selectors supported.
Lets AI use Chrome’s developer tools to inspect pages, find what makes them slow and spot errors. Made by the Chrome DevTools team.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Build with AI. Ship with evidence.
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
| Product overview · 61 seconds | Workflow & evidence · 51 seconds |
|---|---|
| A narrated tour of reusable workflows, agent connections, and sharding. | A fresh local workflow: two passing checks, the report, and screenshot evidence. |
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 → Read the MCP guide →
Your agent / CI / schedule
↓ Environment → Playwright → Pass or fail → Your next action ↓ Report · traces · screenshots · video
Your tests, environments, runners, and next steps. One visible workflow.
| What you need | What Playrunner brings |
|---|---|
| A workflow the team can understand | A visual canvas for tests, conditions, branches, and follow-up actions. |
| Faster feedback from larger suites | Automatic sharding with capacity-aware planning and one merged report. |
| A choice of where tests run | Local Docker, managed cloud runners, and self-hosted execution. |
| A way to investigate a failure | Live node state and logs, plus Playwright reports and captured artefacts. |
| Tests that start signed in | Reusable Authentication Profiles, isolated by environment. |
| Less secret copying | Managed environments and credentials, referenced by your workflows. |
| A useful next step | Integrations for GitHub, Slack, Jira, AI analysis, webhooks, and more. |
Four shards. One merged report. Failed tests stay visible.
Start a saved workflow, stream its progress, and return a failing exit code when the workflow fails, is cancelled, or times out:
export PLAYRUNNER_URL='https://playrunner.cloud'
export PLAYRUNNER_API_KEY=' '
npx playrunner WORKFLOW_ID
Prefer workflows as code? Keep the definition alongside your application:
npx playrunner workflow create --file playrunner-workflow.json
CLI run guide → · Workflow definitions →
Need a signed-in browser? Reuse an Authentication Profile.
Capture a browser session interactively, then select the profile on your Playwright node. Playrunner restores the stored session for the execution without storing your identity-provider password.
For Playrunner Cloud, pair your computer with the authentication companion:
npm install --global playrunner@latest
playrunner login playrunner auth connect
Keep the companion open while capturing or refreshing the session. Hosted workflow runs can restore the encrypted stored state without the companion remaining connected.
Authentication Profiles tutorial →
git clone https://github.com/playrunner/playrunner.git
cd playrunner ./install-local.sh ./start-local.sh
On the first run, Playrunner opens the setup app. Follow the printed URL to confirm PostgreSQL and create the first admin account. With the default ports:
http://127.0.0.1:3100http://127.0.0.1:3100/setuphttp://127.0.0.1:3104/playrunner/The .env.local file is optional unless you want to change ports before the first run. If it is missing, ./start-local.sh creates it from the example. For the complete walkthrough, see the Getting Started guide.
Reopen setup or change the local defaults
To reopen the setup wizard:
./start-local.sh --setup
Remove .env.local as well if you want Playrunner to regenerate the local port and PostgreSQL defaults.
Run only the documentation site
cd docs
npm run start -- --port 3104
Then open http://127.0.0.1:3104/playrunner/.
| Start here | What you will find |
|---|---|
| Automatic sharding | Suite discovery, capacity-aware planning, and report merging |
| Integration reference | Available nodes, providers, and configuration |
| Runner architecture | Local, managed, and self-hosted execution |
| Workflow execution | How the API, orchestrator, and ephemeral runners coordinate |
| Contributing | Ways to extend runners, integrations, reporting, and the product |
Contributing? Run the package end-to-end tests.
Package E2E tests run the real Vite frontend and Playrunner API against the isolated playrunner_e2e PostgreSQL schema. Complete local setup first so apps/api/.env contains a working DATABASE_URL, and keep PostgreSQL running.
Install Chromium once on a new development machine:
npm exec --prefix apps/frontend -- playwright install chromium
Run the deterministic mock-provider suite:
npm run test:e2e:mock
Run one integration package by its Playwright tag:
npm run test:e2e:mock -- --grep @github
npm run test:e2e -- --grep @github
Mock mode still uses the real frontend, authentication, API, credential encryption, and database; only outbound provider boundaries may be faked. Live-provider scenarios are opt-in and require protected credentials:
npm run test:e2e:live
npm run test:e2e:live -- --grep @github
Set PLAYRUNNER_E2E_DATABASE_URL to use another PostgreSQL server. Open the latest report with npx playwright show-report, or read the Testing guide for architecture and package authoring details.
Try it on one workflow that matters to you. Tell us what worked, what failed, and what would make it useful every day.
Join the Discord · Report an issue · Star the project
Playrunner is source-available under the Playrunner Sustainable Use License, copyright © 2026 Concept AI PTY LTD.