E2e Runner runs on your own machine — the client starts it, so there is no endpoint to ping. 53 installs a week from npm. Last commit 8 Jun 2026.
JSON-driven E2E test runner with parallel Chrome pool execution and 16 MCP tools.
We read the source, 20 h ago · rules 3dff92dd89df
A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.
fs.writeFileSync(filePath, JSON.stringify(content, null, 2) + '\n');
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const screenshotPath = path.join(config.screenshotsDir, filename);
const visible = await page.$eval(selector, (e) => {
USER root # Install Node.js 20 (base image ships Node 18, runner requires >=20)
p.innerHTML=highlightJson(text);
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
That is not a flaw by itself — but it is where things go wrong when it is not the job. We re-read this code on every release. Watch it and you hear from us the day another one appears.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add e2e-runner -- npx -y @matware/e2e-runner
{
"mcpServers": {
"e2e-runner": {
"args": [
"-y",
"@matware/e2e-runner"
],
"command": "npx"
}
}
}
[mcp_servers.e2e-runner]
command = "npx"
args = ["-y", "@matware/e2e-runner"]
{
"mcpServers": {
"e2e-runner": {
"args": [
"-y",
"@matware/e2e-runner"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"e2e-runner": {
"args": [
"-y",
"@matware/e2e-runner"
],
"command": "npx"
}
}
}
Undetected anti-bot Chrome automation. 65 tools, parallel isolated browsers.
Browser automation using the user's Chromium session — JS execution, auth, and anti-bot support.
Fetch, parse, screenshot and browse pages via MCP without a real browser -- no JS execution.
Drive your real, logged-in Chrome from any AI agent - 40 tools. Needs our Chrome extension too.
In-browser ~60Hz behavior tree execution engine with reactive triggers and safety guardrails.
Drive Chrome with filesystem commands (ls, cd, grep, click, type). One MCP tool, multi-agent.
MCP server + Chrome extension for AI browser control with real sessions.
Chrome-free MCP web access for agents with low-token page maps and browser escalation hints.
Answers built from our own checks of this server.