How do I install Five46?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Five46 need an API key?

The publisher lists these environment variables: FIVE46_LLM_PROVIDER, FIVE46_LLM_API_KEY, FIVE46_MCP_ALLOW_WRITES, FIVE46_MCP_ALLOW_DELETES, FIVE46_MCP_CONCURRENCY.

What transport does Five46 use?

Five46 runs locally over stdio.

When was Five46 last checked?

Last checked 2026-11-10. BYOK, fully local AI agent that tests your app/API and writes a real Playwright spec on success.

Five46 MCP server

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

npx -y [email protected]

Credentials from the publisher

FIVE46_LLM_PROVIDER — LLM provider to use: openai, anthropic, gemini, groq, or bedrock
FIVE46_LLM_API_KEY — Your own API key for the chosen provider (for bedrock, your AWS region instead)
FIVE46_MCP_ALLOW_WRITES — Set to 1 to unlock POST/PUT/PATCH for the five46_api tool (read-only by default)
FIVE46_MCP_ALLOW_DELETES — Set to 1 to unlock DELETE (five46_api) and destructive-looking browser clicks (five46_test)
FIVE46_MCP_CONCURRENCY — Max concurrent scenarios for story mode (default: 2 for five46_test, 3 for five46_api; hard-capped at 5)

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1FIVE46_LLM_PROVIDER=<value> FIVE46_LLM_API_KEY=<secret> FIVE46_MCP_ALLOW_WRITES=<value> FIVE46_MCP_ALLOW_DELETES=<value> FIVE46_MCP_CONCURRENCY=<value> claude mcp add io.github.sekharsdet-five46 -- npx -y five46@0.2.3

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.sekharsdet-five46": {4      "command": "npx",5      "args": [6        "-y",7        "[email protected]"8      ],9      "env": {10        "FIVE46_LLM_PROVIDER": "<value>",11        "FIVE46_LLM_API_KEY": "<secret>",12        "FIVE46_MCP_ALLOW_WRITES": "<value>",13        "FIVE46_MCP_ALLOW_DELETES": "<value>",14        "FIVE46_MCP_CONCURRENCY": "<value>"15      }16    }17  }18}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

five46

Say what should work, in plain English. An AI agent checks it against your real app or API, using your own LLM key, and hands you a real Playwright test.

five46 driving a real browser through a login, add-to-cart, and checkout flow, then confirming the order was placed

You just built something and want to know whether it actually works, before writing a test. Give five46 a goal like "log in and confirm the dashboard loads" or "create a user via POST, then confirm it via GET". An LLM (OpenAI, Anthropic, Gemini, Groq or AWS Bedrock, with your key) drives your real app or API one action at a time. It tells you honestly whether the goal was met, with a root-cause hypothesis when it wasn't. A successful run is saved as a standalone Playwright (or node:test) spec, so today's check becomes tomorrow's regression test, and running it needs no five46 or LLM.

Quick start

npm install -g five46
npx playwright install chromium   # one-time browser download
five46 config                     # pick a provider and paste a key (Gemini's is free)
five46 doctor                     # confirms the key works
five46 test http://localhost:3000 --goal "log in as [email protected] and confirm the dashboard says Welcome back"

You get a pass or fail (and a matching exit code), a report with screenshots and, for failures, a root-cause hypothesis, plus a five46-agent-*.spec.ts you can commit and run with npx playwright test. Testing an API instead? Use five46 api <base-url> --goal "...". It's read-only unless you pass --allow-writes.

Status: early and actively developed. Verified end-to-end against dozens of real-world sites and APIs.

Check every pull request

The five46 GitHub Action reads the Acceptance criteria section of a pull request's description and checks each item against the PR's preview deployment. It keeps one PR comment up to date with the verdict per criterion, why each failure failed, and a ready-to-commit spec for every criterion that passed.

on: deployment_status   # Vercel, Netlify and other preview deploys
jobs:
  five46:
    if: github.event.deployment_status.state == 'success'
    runs-on: ubuntu-latest
    permissions: { contents: read, pull-requests: write }
    steps:
      - uses: sekharsdet/five46-action@v1
        with:
          url: ${{ github.event.deployment_status.target_url }}
          api-key: ${{ secrets.FIVE46_API_KEY }}

How it compares

	five46	Playwright Test Agents	`playwright codegen`	Cloud AI testing platforms
You provide	A goal or acceptance criteria in plain English	A seed test and a request, inside an AI coding tool	Your own clicks	Test descriptions in their app
Runs	CLI, CI, GitHub Action or MCP tool	Inside an AI coding tool, such as VS Code	Locally, while you click	Their cloud
Built to give a pass/fail verdict on the app	Yes, with a root-cause hypothesis	Not its focus: it generates and repairs tests	No	Yes
API testing	Yes (`node:test` output)	Browser-focused	No	Varies
Proves assertions catch failures	Yes (`--verify` mutation check)	No built-in check	No	Varies
LLM and cost	Your key, any of 5 providers	Your coding agent's model	None	Their subscription
Your app data goes to	Only your LLM provider	Your coding agent's provider	Nowhere	Their platform
Output	Plain Playwright or `node:test` files	Plain Playwright files	Plain Playwright files	Usually their runner

Already working in an AI coding tool and growing a Playwright suite there? Playwright's own agents are a great fit, especially the healer for keeping existing tests green. five46 is for getting a verdict: is this feature working right now, in CI or on a PR, for a browser flow or an API, with any LLM you already pay for. More detail is in Why five46.

Highlights

Safe by default. API runs are read-only unless you unlock writes; destructive-looking clicks ("Delete account") are blocked unless allowed.
Login credentials never reach the LLM. It sees placeholders, and the real values are filled in locally. Log in once, then reuse the session.
Acceptance criteria in, verdicts out. --story splits a user story or ticket into independent scenarios and reports pass/fail per criterion.
Specs you can trust. --verify-clean-session re-runs the spec cold; --verify mutates its assertions and requires them to fail.
Works with any current key. If your provider retires a model, five46 finds a current one your key can use. You can also pin one with FIVE46_LLM_MODEL.
Fits your tools. CI-friendly exit codes, --report JSON for dashboards, flaky-run detection (--repeat), video recording, and an MCP server for IDE assistants.

Docs

Configuration: providers, getting a key, five46 doctor, choosing models
CLI reference: every command and flag, login sessions, API testing, story mode, verification, reports
MCP server: use five46 from an IDE-embedded AI assistant
Security model: what leaves your machine, what five46 guards, and what's your call
Why five46: design choices, the full feature list, comparisons
CHANGELOG

Known limitations

No closed shadow DOM traversal. Elements inside a mode: "closed" shadow root aren't visible to the agent's page snapshot (a closed shadow root is deliberately inaccessible to external tooling in general, not just five46). Open shadow roots, the overwhelming majority of real-world web components, work fine, as do <iframe> and <frame> content.
Chromium only for browser mode, with no Firefox or WebKit yet.
A run itself is not deterministic. The same goal against the same page can take a different path next time. The generated spec is the frozen, repeatable artifact.

Contributing

Issues and pull requests are welcome. See CONTRIBUTING.md.

git clone https://github.com/sekharsdet/five46.git
cd five46
npm install
npm run build
node dist/cli.js test <url> --goal "..."
npm test

If five46 is useful to you, a ⭐ on GitHub helps other people find it.

License

MIT

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Five46?

Does Five46 need an API key?

What transport does Five46 use?

When was Five46 last checked?

Documentation

five46

Quick start

Check every pull request

How it compares

Highlights

Docs

Known limitations

Contributing

License