How do I install Playrunner?

Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Playrunner need an API key?

No required environment variable is listed on this record.

What transport does Playrunner use?

Playrunner is reached over HTTP.

When was Playrunner last checked?

Last checked 2026-11-08. Discover Playwright workflows, start runs, and inspect results in Playrunner Cloud.

Playrunner MCP server

Power your agent

Add this server

The publisher's own URL. Not a PlugMCP endpoint.

Add to Cursor Add in Claude Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Server URL

https://playrunner.cloud/mcp

The Claude button above opens Claude with the name and URL filled in. You still confirm it there.

shClaude Code

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

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "dev.playrunner-mcp": {4      "command": "npx",5      "args": [6        "-y",7        "mcp-remote",8        "https://playrunner.cloud/mcp"9      ]10    }11  }12}

claude_desktop_config.json

Remote · HTTPPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Remote

Transport: http
Version: 0.1.1
Last checked

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

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

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

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.

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

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='<your-api-token>'

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 →

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.

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.

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

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

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Playrunner?

Does Playrunner need an API key?

What transport does Playrunner use?

When was Playrunner last checked?

Documentation

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