E2e Runner

E2e Runner runs locally from a Node.js package published to the npm registry: @matware/e2e-runner version 1.3.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y @matware/e2e-runner@1.3.0.

E2e Runner runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: docker.io/fastslack/e2e-runner-mcp:1.3.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run — the usual command is docker run -i --rm docker.io/fastslack/e2e-runner-mcp:1.3.0.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "e2e-runner": {
      "command": "npx",
      "args": [
        "-y",
        "@matware/e2e-runner@1.3.0"
      ]
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect