Playrunner

dev.playrunner由 playrunner.dev 发布v0.1.1更新于 Oct 24, 2026

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

已验证Streamable HTTP可网页运行云端与基础设施浏览器自动化开发者工具

概览

AI 生成的概览

Playrunner Cloud 的 MCP 服务器，让助手发现 Playwright 工作流、启动测试运行，并查看报告、追踪与产物。

可以做什么
  • 发现 Playrunner Cloud 中的项目与已保存的 Playwright 工作流
  • 用现有测试或内联脚本创建工作流，并指定环境与认证配置
  • 启动工作流运行并跟踪执行进度
  • 查看结果：哪些测试通过或失败，以及日志、报告、追踪、截图和视频
适用场景
适合团队把 Playwright 测试放在 Playrunner 中，希望助手在改动后触发一次检查，并带回哪些通过、哪些失败以及证据链接，而不只是确认代码写完了。
运行要求
需要 playrunner.cloud 的远程 Streamable HTTP 端点与 OAuth 登录，客户端须支持远程 Streamable HTTP 和 OAuth。需要 Playrunner 账号以及已有的项目或工作流。可选的 CLI 与本地整套环境需要 Node.js 20+、npm 和 Docker Desktop。
安装前请注意
助手可以创建工作流并启动运行，会占用执行资源，云端运行可能产生费用。工作流可引用托管环境与已保存的凭据，认证配置会恢复已保存的浏览器会话；让助手运行前应确认工作流能访问什么。已启动的任务不等于测试通过，结果需要实际查看。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Playrunner，将其添加到工作区。
  2. 连接 所需的 凭据。它们会被私密存储，绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/dev.playrunner%2Fmcp/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。

{
  "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.

来源：README.md，提交 0eb61b8

工具

0
该服务器需要登录，因此 SourceWeft 无法在没有账号的情况下读取其工具，也未收录。已连接账号所能看到的内容可能因账号及其权限而异。

版本历史

1
  1. v0.1.1最新Sep 16, 2026

评分

已满足适用检查项的 75%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。