x=hub

your toolset

    build deployment
    sign in

    TabRunner

    mcpkey · package official
    app.tabrunner/tabrunner · v0.13.0
    deploy just this

    Give browser tasks to TabRunner, an agent in your own Chrome that uses your logins.

    run it

    on your own machines, one way per deploy method
    generated from the record, not tested yet
    # once, as root:
    # as_mcp DIR COMMAND...: runs COMMAND as the mcp user in DIR, its home, sandboxed as the
    # units are: a package's install scripts can write to DIR only, as the server later can
    as_mcp() {
      local dir="$1"; shift
      systemd-run --quiet --wait --pipe --collect --uid=mcp --gid=mcp \
        -p WorkingDirectory="$dir" -p Environment=HOME="$dir" -p ReadWritePaths="$dir" \
        -p NoNewPrivileges=true -p ProtectSystem=strict -p ProtectHome=true -p PrivateTmp=true \
        -- "$@" </dev/null
    }
    install -d -m 0750 -o mcp -g mcp /var/lib/mcp/tabrunner
    # tabrunner: its packages, installed whole before its unit starts (no session installs)
    # npx takes a half-installed tree for installed: a rerun starts them afresh
    systemctl stop mcp-my-agent-tabrunner.service 2>/dev/null || true
    as_mcp /var/lib/mcp/tabrunner rm -rf /var/lib/mcp/tabrunner/.npm/_npx
    as_mcp /var/lib/mcp/tabrunner npx --yes [email protected] -- true
    as_mcp /var/lib/mcp/tabrunner npx --yes --package=supergateway@4 -- true
    
    #!/usr/bin/env bash
    # tabrunner (app.tabrunner/tabrunner), recipe baremetal (generated).
    # Generated by Hub for toolset "my-agent"; started by mcp-my-agent-tabrunner.service.
    set -euo pipefail
    export HOST=127.0.0.1 PORT=8101
    exec npx -y supergateway@4 --stdio 'npx -y [email protected]' --outputTransport streamableHttp --stateful --host 127.0.0.1 --port 8101 --streamableHttpPath /mcp --healthEndpoint /healthz
    
    [Unit]
    Description=MCP server tabrunner (toolset my-agent), generated by Hub
    After=network-online.target
    Wants=network-online.target
    
    [Service]
    Type=simple
    User=mcp
    Group=mcp
    EnvironmentFile=/etc/mcp/my-agent.env
    Environment=HOME=/var/lib/mcp/tabrunner
    WorkingDirectory=/var/lib/mcp/tabrunner
    ExecStart=/opt/mcp/my-agent/bin/tabrunner.sh
    Restart=on-failure
    RestartSec=5
    NoNewPrivileges=true
    ProtectSystem=strict
    ProtectHome=true
    PrivateTmp=true
    ReadWritePaths=/var/lib/mcp/tabrunner
    
    [Install]
    WantedBy=multi-user.target
    
    generated from the record, not tested yet
    docker run --rm -p 127.0.0.1:8101:8000 -e TABRUNNER_BRIDGE_PORT node:22-alpine sh -c 'npx -y supergateway@4 --stdio '"'"'npx -y [email protected]'"'"' --outputTransport streamableHttp --stateful --host 0.0.0.0 --port 8000 --streamableHttpPath /mcp --healthEndpoint /healthz'
    
    generated from the record, not tested yet
    # Generated by Hub for toolset "my-agent" (2026-10-19T12:05:19+00:00).
    # Each package server runs behind a stdio->HTTP bridge and listens on localhost only.
    #   cp .env.example .env    # fill the ${VAR}s
    #   docker compose up -d && bash smoke.sh
    # Remote servers are not here: clients reach them directly (see clients/).
    name: mcp-my-agent
    services:
      tabrunner:
        image: node:22-alpine
        command:
        - sh
        - -c
        - npx -y supergateway@4 --stdio 'npx -y [email protected]' --outputTransport streamableHttp --stateful
          --host 0.0.0.0 --port 8000 --streamableHttpPath /mcp --healthEndpoint /healthz
        ports:
        - 127.0.0.1:8101:8000
        volumes:
        - npm-cache:/root/.npm
        healthcheck:
          test:
          - CMD-SHELL
          - wget -qO- http://127.0.0.1:8000/healthz || exit 1
          interval: 30s
          timeout: 5s
          retries: 5
          start_period: 2m
        restart: unless-stopped
        environment:
          TABRUNNER_BRIDGE_PORT: ${TABRUNNER_BRIDGE_PORT}
    volumes:
      npm-cache: {}
      uv-cache: {}
    
    generated from the record, not tested yet
    # Generated by Hub for toolset "my-agent" (2026-10-19T12:05:19+00:00).
    #   kubectl create namespace mcp
    #   kubectl -n mcp create secret generic mcp-credentials --from-env-file=.env
    #   kubectl apply -f kubernetes.yaml
    # Services are cluster-internal: <name>.mcp.svc.cluster.local:8000/mcp. Put an ingress
    # with auth in front before exposing any of them.
    apiVersion: v1
    kind: Namespace
    metadata:
      name: mcp
    ---
    apiVersion: apps/v1
    kind: Deployment
    metadata:
      name: tabrunner
      namespace: mcp
      labels: &id001
        app: tabrunner
    spec:
      replicas: 1
      selector:
        matchLabels: *id001
      template:
        metadata:
          labels: *id001
        spec:
          containers:
          - name: tabrunner
            image: node:22-alpine
            ports:
            - containerPort: 8000
              name: http
            env:
            - name: TABRUNNER_BRIDGE_PORT
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: TABRUNNER_BRIDGE_PORT
            args:
            - sh
            - -c
            - npx -y supergateway@4 --stdio 'npx -y [email protected]' --outputTransport streamableHttp
              --stateful --host 0.0.0.0 --port 8000 --streamableHttpPath /mcp --healthEndpoint /healthz
            readinessProbe:
              httpGet:
                path: /healthz
                port: http
              initialDelaySeconds: 10
    ---
    apiVersion: v1
    kind: Service
    metadata:
      name: tabrunner
      namespace: mcp
    spec:
      selector:
        app: tabrunner
      ports:
      - port: 8000
        targetPort: http
        name: http
    
    generated from the record, not tested yet
    # Generated by Hub for toolset "my-agent" (2026-10-19T12:05:19+00:00).
    # Credentials come from the Secret 'mcp-credentials' (kubectl create secret generic ... --from-env-file=.env).
    # Each server under `servers` is one Deployment + Service; the keys after it configure
    # upstream charts a worker verified.
    servers:
      tabrunner:
        enabled: true
        replicas: 1
        port: 8000
        path: /mcp
        container:
          name: tabrunner
          image: node:22-alpine
          ports:
          - containerPort: 8000
            name: http
          env:
          - name: TABRUNNER_BRIDGE_PORT
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: TABRUNNER_BRIDGE_PORT
          args:
          - sh
          - -c
          - npx -y supergateway@4 --stdio 'npx -y [email protected]' --outputTransport streamableHttp --stateful
            --host 0.0.0.0 --port 8000 --streamableHttpPath /mcp --healthEndpoint /healthz
          readinessProbe:
            httpGet:
              path: /healthz
              port: http
            initialDelaySeconds: 10
    
    # helm install my-agent helm/my-agent -n mcp
    

    in the cloud

    one click: the provider's deploy form opens filled in, in your own account
    koyeb

    The form opens with CHANGE_ME for each value you supply: TABRUNNER_BRIDGE_PORT. Fill them in before you deploy.

    Clients connect to the service's https://…koyeb.app address plus /mcp.

    azure

    A Container Apps environment with one app per server, each with HTTPS ingress and one replica. The portal asks for each value you supply as a secure parameter; the deployment's outputs list the endpoints.

    connect to it

    copy what your client needs
    npx -y [email protected]
    # env: TABRUNNER_BRIDGE_PORT
    {
      "mcpServers": {
        "tabrunner": {
          "command": "npx",
          "args": [
            "-y",
            "[email protected]"
          ],
          "env": {
            "TABRUNNER_BRIDGE_PORT": "${TABRUNNER_BRIDGE_PORT}"
          }
        }
      }
    }
    #!/usr/bin/env bash
    # Registers every server with Claude Code (run once; `claude mcp list` to check).
    set -euo pipefail
    set -a; [ -f .env ] && source .env; set +a
    claude mcp add tabrunner -e "TABRUNNER_BRIDGE_PORT=${TABRUNNER_BRIDGE_PORT}" -- npx -y [email protected]
    
    {
      "mcpServers": {
        "tabrunner": {
          "command": "npx",
          "args": [
            "-y",
            "[email protected]"
          ],
          "env": {
            "TABRUNNER_BRIDGE_PORT": "${TABRUNNER_BRIDGE_PORT}"
          }
        }
      }
    }
    {
      "servers": {
        "tabrunner": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "[email protected]"
          ],
          "env": {
            "TABRUNNER_BRIDGE_PORT": "${TABRUNNER_BRIDGE_PORT}"
          }
        }
      }
    }
    name: my-agent
    target: local
    servers:
    - hub: app.tabrunner/tabrunner
    
    • not probed yet: tools unpinned, ingest lists them

    tools

    Probe result: faileddocker: no MCP server found (:8000/mcp: HTTP 404: MCPError: MCP server process failed; :8000/: HTTP 404: MCPError: Not Found) [UNDICI-EHPA] Warning: EnvHttpProxyAgent is experimental, expect them to change at any time. (Use `node --trace-warnings ...` to show where the warning was created) [supergateway] Child stderr: env: can't execute 'bun': No such file or directory [supergateway] Child exited: code=127, signal=null; baremetal: MCPError: Connection closed; server stderr: …(node:1) [UNDICI-EH…

    runs · 1

    the latest tests of this entry by the hub and its workers, newest first
    dateworkermethodstatussandboxreason
    2026-10-18 00:25 local-mac-vm docker failed gvisor docker: no MCP server found (:8000/mcp: HTTP 404: MCPError: MCP server process failed; :8000/: HTTP 404: MCPError: Not Found) [UNDICI-EHPA] Warning: EnvHttpProx…