에이전트 강화
게시자의 자체 명령입니다. PlugMCP 엔드포인트가 아닙니다.
Host a copy with our keys and logs.
npx -y [email protected]Claude Code에는 로컬 명령용 설치 링크가 없습니다. 아래 명령을 복사해 터미널에서 실행합니다.
FIVE46_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터미널에서 실행합니다.
{ "mcpServers": { "io.github.sekharsdet-five46": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "FIVE46_LLM_PROVIDER": "<value>", "FIVE46_LLM_API_KEY": "<secret>", "FIVE46_MCP_ALLOW_WRITES": "<value>", "FIVE46_MCP_ALLOW_DELETES": "<value>", "FIVE46_MCP_CONCURRENCY": "<value>" } } }}claude_desktop_config.json
원격 URL인가요, 내 컴퓨터에서 실행하는 명령인가요? 두 설치 방식의 차이
PlugMCP에서 실행
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.
실행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.

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.
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.
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 }}
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.
--story splits a user story
or ticket into independent scenarios and reports pass/fail per criterion.--verify-clean-session re-runs the spec cold;
--verify mutates its assertions and requires them to fail.FIVE46_LLM_MODEL.--report JSON for
dashboards, flaky-run detection (--repeat), video recording, and an
MCP server for IDE assistants.five46 doctor, choosing modelsmode: "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.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.
BYOK, fully local AI agent that tests your app/API and writes a real Playwright spec on success.
{ "mcpServers": { "io.github.sekharsdet-five46": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "FIVE46_LLM_PROVIDER": "<value>", "FIVE46_LLM_API_KEY": "<secret>", "FIVE46_MCP_ALLOW_WRITES": "<value>", "FIVE46_MCP_ALLOW_DELETES": "<value>", "FIVE46_MCP_CONCURRENCY": "<value>" } } }}도구
아직 도구 목록이 없습니다. 원격 서버는 첫 상태 확인 후에 도구 목록이 생깁니다.
FAQ
이 페이지에서 Cursor, Claude Desktop, Claude Code 또는 VS Code용 stdio 설정을 복사합니다. PlugMCP 프록시가 아니라 게시자의 설치 방식을 사용합니다.
게시자가 등록한 환경 변수: FIVE46_LLM_PROVIDER, FIVE46_LLM_API_KEY, FIVE46_MCP_ALLOW_WRITES, FIVE46_MCP_ALLOW_DELETES, FIVE46_MCP_CONCURRENCY.
Five46은(는) stdio를 통해 로컬에서 실행됩니다.
마지막 확인: 2026-11-10. BYOK, fully local AI agent that tests your app/API and writes a real Playwright spec on success.