auten-ai/auten-mcp

[
  {
    "status": "PASS",
    "details": {
      "working": false,
      "argv": [
        "<host-path>",
        "--version"
      ],
      "kind": "cli",
      "returncode": 0,
      "stdout": "auten 1.0",
      "stderr": "",
      "needs_credentials": false,
      "needs_browser": false,
      "scope": "partial: install"
    },
    "check": "install",
    "optional": false
  },
  {
    "status": "FAIL",
    "details": {
      "working": false,
      "argv": [
        "<host-path>",
        "mcp-bridge"
      ],
      "kind": "mcp",
      "blocker": "MCP response missing for request 1: argv did not answer as a stdio MCP server (a client CLI that talks to servers is kind cli); stderr: auten: no key on this device \u2014 run `auten login` in a terminal first\n"
    },
    "check": "credentials_error",
    "optional": false
  }
]

Installed the Auten runner via README 'curl -fsSL https://auten.ai/install | bash' (with AUTEN_NO_LAUNCH=1 per llms-install.md) and ran 'auten --version' (auten 1.0). Attempted MCP start via 'auten mcp-bridge' (stdio) for initialize + tools/list.

cd <host-path> && git log -1 --format=%H 2>/dev/null; ls -la; cat README.md 2>/dev/null | head -300
cat <host-path> | head -80; ls <host-path>
cd <host-path> && sed -n 300,400p README.md; echo ----; cat llms-install.md; echo ----; cat package.json; ls bin examples .github/workflows; cat bin/* | head -80
cd <host-path> && node -v; npm -v; echo "DISPLAY=$DISPLAY"; echo "CDP_URL=$CDP_URL"; whoami; (sudo -n true && echo sudo_ok) 2>&1; sudo apt-get update 2>&1 | tail -3 && sudo DEBIAN_FRONTEND=noninteractive apt-get install -y python3-venv python3-pyatspi python3-gi xdotool wmctrl scrot xclip libglib2.0-bin tesseract-ocr libsecret-tools 2>&1 | tail -5
cd <host-path> && curl -fsSL https://auten.ai/install -o /tmp/auten-install.sh; echo "dl=$?"; wc -c /tmp/auten-install.sh; (AUTEN_NO_LAUNCH=1 bash /tmp/auten-install.sh) 2>&1 | tail -40; echo "rc=${PIPESTATUS[0]}"; ls -la ~/.local/bin/auten 2>&1
export PATH="$HOME/.local/bin:$PATH"; auten status 2>&1 | head -30; echo ---; printf '%s\n' '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"smoke","version":"0"}}}' '{"jsonrpc":"2.0","method":"notifications/initialized"}' '{"jsonrpc":"2.0","id":2,"method":"tools/list"}' | timeout 60 auten mcp-bridge 2>/tmp/bridge.err | head -c 3000; echo; echo "rc=$?"; head -c 1500 /tmp/bridge.err
cd <host-path> && grep -n "credentials_error\|'checks'\|\"checks\"\|def \|validate" check.py | head -80
cd <host-path> && sed -n 75,102p check.py; sed -n 377,470p check.py; sed -n 511,546p check.py
export PATH="$HOME/.local/bin:$PATH"; cd <host-path>; auten --version </dev/null; echo "rc=$?"; auten mcp-bridge </dev/null >/tmp/b.out 2>/tmp/b.err; echo "rc=$?"; cat /tmp/b.out; cat /tmp/b.err
cd <host-path> && mkdir -p .coldpass && cat > .coldpass/probe.json <<'EOF'
{"checks":[
 {"check":"install","kind":"cli","argv":["<host-path>"},
 {"check":"credentials_error","kind":"mcp","argv":["<host-path>"}
]}
EOF
cat > .coldpass/report.json <<'EOF'
{"outcome":"needs_credentials",
 "operation":"Installed the Auten runner via README 'curl -fsSL https://auten.ai/install | bash' (with AUTEN_NO_LAUNCH=1 per llms-install.md) and ran 'auten --version' (auten 1.0). Attempted MCP start via 'auten mcp-bridge' (stdio) for initialize + tools/list.",
 "operation_scope":"Install passed. MCP start/tools-list not reached: mcp-bridge exits 1 with 'no key on this device — run `auten login` in a terminal first'. Needs a user-issued Auten key (auten login, free plan, browser sign-in). Not obtained; no credentials were sought. Also no X11 DISPLAY in the VM (README: headless needs a display), so GUI tools would not work even with a key.",
 "steps":["sudo apt-get update","sudo apt-get install -y python3-venv python3-pyatspi python3-gi xdotool wmctrl scrot xclip libglib2.0-bin tesseract-ocr libsecret-tools","curl -fsSL https://auten.ai/install -o /tmp/auten-install.sh && AUTEN_NO_LAUNCH=1 bash /tmp/auten-install.sh (Installed; binary at ~/.local/bin/auten)","auten --version -> auten 1.0","auten mcp-bridge (stdio initialize/tools/list) -> exit 1, no key on this device"],
 "deviations":["Node/npm not installed in guest; the npx launcher (bin/auten-mcp.js) was not used. Used the native 'auten mcp-bridge' entry from README Client setup instead.","'auten status' without a key entered the interactive first-run menu and cancelled on stdin EOF; used 'auten --version' for the install check instead.","Install script was downloaded to /tmp and run with AUTEN_NO_LAUNCH=1 rather than piped directly, to read exit status."],
 "stuck_step":"README Quick start step 2 / llms-install.md Step 2: 'auten login' (user must connect a key)",
 "main_blocker":"No Auten key on this device; mcp-bridge refuses to start. Also no X11 display (DISPLAY unset).",
 "suggested_fix":"A user with an Auten account runs 'auten login' in a terminal on the guest (or supplies a key via the documented mechanism), and an X11 display (e.g. Xvfb plus DISPLAY) is provided. Then rerun: printf initialize/tools/list JSON-RPC lines into '<host-path> mcp-bridge'."}
EOF
<env-var>=<host-path> python3 -I <host-path> --validate