Greenrun

Name: Greenrun
Author: Add-Item-To

@Add-Item-To

リポジトリホームページ

Greenrun について

Browser test management for Claude Code. Write tests in plain English, run them with /greenrun.

#browser-testing #claude-code #playwright #e2e-testing #natural-language #mcp #testing

基本情報

カテゴリ

開発者ツール

ライセンス

MIT

ランタイム

node

トランスポート

stdio

公開者

Add-Item-To

投稿者

Stewis

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "greenrun": {
      "command": "npx",
      "args": [
        "greenrun-cli"
      ]
    }
  }
}

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Greenrun?

Greenrun is an MCP server that connects Claude Code to the Greenrun API for browser test management. You describe tests in plain English, and Claude generates and runs Playwright scripts automatically, handling script generation, parallel execution, result tracking, and re-running only what's needed.

How to use Greenrun?

Run npx greenrun-cli init to launch an interactive setup wizard that validates your API token, configures the Greenrun and Playwright MCP servers, installs slash commands, and adds project instructions. Tests are defined in the Greenrun dashboard or via MCP tools, then executed by running /greenrun in Claude Code. Manual setup is also supported via claude mcp add or .mcp.json.

Key features of Greenrun

Write tests in plain English, no Playwright code needed
Claude generates Playwright scripts on first run
Cached scripts skip generation on subsequent runs
Parallel test execution with result tracking
Impact analysis via /greenrun-sweep for changed pages
Named credential sets for authentication per test
Test filtering by tag, URL path, or name

Use cases of Greenrun

Define and run end-to-end browser tests without writing code
Quickly re-run only the tests affected by recent code changes
Manage test suites across multiple projects with credential management
Integrate browser testing directly into Claude Code workflows

FAQ from Greenrun

What are the prerequisites for using Greenrun?

Node.js 18+, Claude Code, and the Playwright MCP server (configured automatically by the init wizard).

How does Greenrun generate test scripts?

On the first run, Claude walks through each test's instructions in the browser, observes UI states, and generates a .spec.ts script with real selectors. The script is cached and reused on future runs.

How does Greenrun handle test failures due to stale scripts?

If a cached script fails, an AI agent re-executes the test manually to determine whether the script is stale or there is a real bug. Stale scripts are automatically cleared for regeneration.

How does Greenrun handle authentication?

Projects support named credential sets (name, email, password). Each test can reference a credential by name via credential_name, and during execution the matching credentials are used to authenticate.

How can I run only tests affected by recent code changes?

Run the /greenrun-sweep slash command. It detects which tests are impacted by the pages you changed (based on git changes) and offers to run only those tests.