Mtw E2e Runner MCP Server

E2E test runner using Chrome Pool (browserless/chrome) with parallel execution

Local serverstdio

What is the Mtw E2e Runner MCP server?

If you already use Mtw E2e Runner, the mtw e2e runner mcp server is the piece that lets your assistant work with it directly. E2E test runner using Chrome Pool (browserless/chrome) with parallel execution.

What the server does

The AI-native E2E test runner that writes, runs, and debugs tests for you.

Installation

The server ships on npm as skills, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Action — Fields
  • goto — value
  • click — selector or text
  • wait — selector, text, gone, or value (ms)
  • screenshot — value (filename)
  • select — selector, value
  • clear — selector
  • press — value
  • scroll — selector or value (px)
  • hover — selector
  • evaluate — value
  • navigate — value

Credentials and setup notes

Configuration is passed through the environment: CHROME_POOL_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Mtw E2e Runner.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

This sits in the browser automation group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Mtw E2e Runner's toolset — Action, goto, click and 11 more — is a fair guide to whether it matches your workflow. It is maintained by fastslack; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Mtw E2e Runner's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
ActionFields
gotovalue
clickselector or text
waitselector, text, gone, or value (ms)
screenshotvalue (filename)
selectselector, value
clearselector
pressvalue
scrollselector or value (px)
hoverselector
evaluatevalue
navigatevalue
clear_cookies
wait_network_idleoptional value (idle ms, default 500), timeout

How to install the Mtw E2e Runner MCP server

{
  "mcpServers": {
    "mtw-e2e-runner": {
      "command": "npx",
      "args": ["-y", "skills"],
      "env": {
        "CHROME_POOL_URL": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
CHROME_POOL_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Mtw E2e Runner to Action.
  • Use Mtw E2e Runner to goto.
  • Use Mtw E2e Runner to click.

Frequently asked questions

It connects Mtw E2e Runner to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (Action, goto, click, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Mtw E2e Runner directly.