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 分

    請在儲存庫或註冊中心條目中宣告授權條款。