Playrunner

Name: Playrunner
Author: playrunner

by playrunnerversion 0.1.1i★ –iRuns in the cloud

Registry namedev.playrunner/mcp

Install

Overview

Description from the maker (original English)

Discover Playwright workflows, start runs, and inspect results in Playrunner Cloud.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs in the cloud
Transport: Streamable HTTP
Category: Web & browsers

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
The registry lists no key to fill in.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://playrunner.cloud/mcp

Run this in your terminal

claude mcp add --transport http playrunner https://playrunner.cloud/mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "playrunner": {
      "url": "https://playrunner.cloud/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "playrunner": {
      "type": "http",
      "url": "https://playrunner.cloud/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://playrunner.cloud/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

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 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain playrunner.dev (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Web & browsersi

More stars than 0% of the other 875 servers in this category
Published to the registry more recently than 40% of the other 875 servers in this category
Basic checks equal to or better than 100% of the other 875 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Playrunner safe?

It passed 1 of 1 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.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

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.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 2 months ago.

Which apps can use it?

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 in developer mode.

What can I use instead?

In the same category: Browser Use, Chrome DevTools MCP, MCP Server Browser

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Browser Use

by 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.

Computer or cloud★ 120,087MITUpdated 16 days ago

Install

Chrome DevTools MCP

by ChromeDevTools

Lets AI use Chrome’s developer tools to inspect pages, find what makes them slow and spot errors. Made by the Chrome DevTools team.

Runs on your computer★ 54,821Apache-2.0Updated 15 days ago

Install

MCP Server Browser

by bytedance

MCP server for browser use access

Runs on your computer★ 39,550Apache-2.0Updated 14 months ago

Install

README from the maker

Open the README

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

See Playrunner in a minute

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 →

Your agent wrote it. Now check it.

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.

For vibe coders and their favourite agents

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 →

From a test suite to a repeatable check

Bring a test. Use your existing Playwright repository or start with an inline script.
Give it a home. Choose an environment, an optional Authentication Profile, and where the workflow runs.
Run it your way. Use the visual editor, your agent, the CLI, or a schedule.
Follow the evidence. Inspect test results, logs, and the report and artefacts produced by the run. A started job is not a passing test.

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.

Less test infrastructure. More useful feedback.

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.

Give your CI the same workflow

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 →

Quick start

Prerequisites

Docker Desktop
Node.js 20+
npm

Start the full local stack

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:

Playrunner: http://127.0.0.1:3100
Setup: http://127.0.0.1:3100/setup
Documentation: http://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/.

Explore

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.

Help shape Playrunner

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

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Web & browsersi

Common questions

Alternatives

Browser Use

Chrome DevTools MCP

MCP Server Browser

README from the maker

See Playrunner in a minute

Your agent wrote it. Now check it.

For vibe coders and their favourite agents

From a test suite to a repeatable check

Less test infrastructure. More useful feedback.

Give your CI the same workflow

Quick start

Prerequisites

Start the full local stack

Explore

Help shape Playrunner

License