JSON-driven E2E test runner with parallel Chrome pool execution and 16 MCP tools.
npx -y @matware/e2e-runnerAdd this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"io-github-fastslack-e2e-runner": {
"command": "npx",
"args": [
"-y",
"@matware/e2e-runner"
]
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
e2e-runner is an MCP server for JSON-driven E2E test runner with parallel Chrome pool execution and 16 MCP tools.. It supports STDIO transport.
Use the generated config in Install. This server runs with npx -y @matware/e2e-runner; add any required environment variables before starting your client.
Choose the Claude Desktop tab in Install and copy the config for npx -y @matware/e2e-runner. Add required environment variables before starting Claude Desktop.
Choose the Claude Code tab in Install and copy the config for npx -y @matware/e2e-runner. Add required environment variables before starting Claude Code.
Choose the Codex tab in Install and copy the config for npx -y @matware/e2e-runner. Add required environment variables before starting Codex.
Choose the Cursor or VS Code tab in Install and copy the config for npx -y @matware/e2e-runner. Add required environment variables before starting Cursor or VS Code.
e2e-runner uses STDIO transport. Use the package or command config in Install.
e2e-runner inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
e2e-runner does not advertise a verified auth requirement. If discovery fails, it may still need provider login, an API key, a bearer token, or a session header.
| Package | Registry | Version | Inputs |
|---|---|---|---|
@matware/e2e-runnerstdio | npm | 1.3.0 | None advertised |
docker.io/fastslack/e2e-runner-mcp:1.3.0stdio | oci | Not captured | None advertised |