Playrunner

dev.playrunnerPublished by playrunner.devv0.1.1Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableCloud & InfrastructureBrowser AutomationDeveloper Tools

Overview

AI-generated overview

Playrunner Cloud MCP server that lets an assistant discover Playwright workflows, start test runs, and inspect reports, traces and artefacts.

What you can do
  • Discover projects and saved Playwright workflows in Playrunner Cloud
  • Create workflows from existing tests or inline scripts, with environments and authentication profiles
  • Start workflow runs and follow their execution progress
  • Inspect results: which tests passed or failed, logs, reports, traces, screenshots and video
When to use it
Useful when a team keeps Playwright tests in Playrunner and wants an agent to trigger a check after a change and report back what passed or failed with evidence links, rather than just confirming the code looks done.
Requirements
A remote Streamable HTTP endpoint at playrunner.cloud with OAuth sign-in; the client must support remote Streamable HTTP and OAuth. A Playrunner account and existing projects or workflows are needed. The optional CLI and local stack need Node.js 20+, npm and Docker Desktop.
Before you install
The assistant can create workflows and start runs, which consume runner capacity and may incur cloud usage. Workflows can reference managed environments and stored credentials, and Authentication Profiles restore saved browser sessions; review what a workflow can reach before letting an agent run it. A started job is not a passing test, so results should be checked rather than assumed.

Installation

In SourceWeft

  1. Open Playrunner in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.playrunner%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

README

[Playrunner]

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

[Discord] [Playrunner on YouTube] [npm packages]

See Playrunner in a minute

Product overview · 61 secondsWorkflow & evidence · 51 seconds
[Watch the narrated Playrunner overview][Watch a real workflow and its test evidence]
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

  1. Bring a test. Use your existing Playwright repository or start with an inline script.
  2. Give it a home. Choose an environment, an optional Authentication Profile, and where the workflow runs.
  3. Run it your way. Use the visual editor, your agent, the CLI, or a schedule.
  4. Follow the evidence. Inspect test results, logs, and the report and artefacts produced by the run. A started job is not a passing test.
text
Your agent / CI / schedule           ↓      Environment → Playwright → Pass or fail → Your next action                         ↓              Report · traces · screenshots · video

[A visual Playrunner workflow connects browser tests to failure analysis, issue tracking, and notifications.]

Your tests, environments, runners, and next steps. One visible workflow.

Less test infrastructure. More useful feedback.

What you needWhat Playrunner brings
A workflow the team can understandA visual canvas for tests, conditions, branches, and follow-up actions.
Faster feedback from larger suitesAutomatic sharding with capacity-aware planning and one merged report.
A choice of where tests runLocal Docker, managed cloud runners, and self-hosted execution.
A way to investigate a failureLive node state and logs, plus Playwright reports and captured artefacts.
Tests that start signed inReusable Authentication Profiles, isolated by environment.
Less secret copyingManaged environments and credentials, referenced by your workflows.
A useful next stepIntegrations for GitHub, Slack, Jira, AI analysis, webhooks, and more.

[A Playwright node splits a suite into four shards and merges the report, including a failed shard.]

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:

bash
export PLAYRUNNER_URL='https://playrunner.cloud'export PLAYRUNNER_API_KEY='<your-api-token>'
npx playrunner WORKFLOW_ID

Prefer workflows as code? Keep the definition alongside your application:

bash
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:

bash
npm install --global playrunner@latestplayrunner loginplayrunner 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

bash
git clone https://github.com/playrunner/playrunner.gitcd 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:

bash
./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
bash
cd docsnpm run start -- --port 3104

Then open http://127.0.0.1:3104/playrunner/.

Explore

Start hereWhat you will find
Automatic shardingSuite discovery, capacity-aware planning, and report merging
Integration referenceAvailable nodes, providers, and configuration
Runner architectureLocal, managed, and self-hosted execution
Workflow executionHow the API, orchestrator, and ephemeral runners coordinate
ContributingWays 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:

bash
npm exec --prefix apps/frontend -- playwright install chromium

Run the deterministic mock-provider suite:

bash
npm run test:e2e:mock

Run one integration package by its Playwright tag:

bash
npm run test:e2e:mock -- --grep @githubnpm 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:

bash
npm run test:e2e:livenpm 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

License

Playrunner is source-available under the Playrunner Sustainable Use License, copyright © 2026 Concept AI PTY LTD.

Source: README.md at commit 0eb61b8

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.