MCP

Test your build with agents

Right from your terminal.

Same server, any agent.

One config block, then restart.

Run this in your project root

claude mcp add fraser \
  --env FRASER_API_KEY=your-token \
  --env FRASER_API_URL=https://fraser.lythe.ai \
  -- uvx --from fraser-gate@latest fraser-gate-mcp

fraser-gate — mcp — 96×24

[x] Persona cast ready

[x] Funnel report

> fraser_start_review https://staging.myapp.com

run 8c21f0 · 5 personas · goal: reach the dashboard

> fraser_get_status

persona 3 of 5 · comparing plans on /pricing

> fraser_get_findings

3 findings · 2 of 5 reached the goal

> fraser_validate_fix

2 fixed · 1 regressed · gate: blocked

→ Add a follow-upesc to stop
• Gate (shift+tab to cycle)
fraser-gate · 5 personas · 100%
/ commands · @ personas · ! shell

Fraser

~/apps/web

> Review the signup flow on staging

fraser_start_review

fraser_get_status

fraser_get_findings

fraser_get_report

fraser_validate_fix

fraser_get_validation

Run it from a sentence

Point your agent at a URL. Fraser writes ICP personas from your product and drives a real browser as each one.

fraser_get_findings

highPlan choice unclear on /pricing3/5
medEmail verification stalls signup2/5
lowPricing FAQ answers the wrong thing1/5
reached the goal2 / 5

Read where users broke

Where each persona hesitated, misread or lost trust, with evidence and screenshots, plus a funnel of who reached the goal.

lythe-labs / web

CodePull requestsFraser
FixedPlan choice unclear on /pricing
FixedEmail verification stalls signup
RegressedNav overlaps the CTA on mobile

Gate the merge on the result

Re-run the identical cast against the fix. Every finding comes back fixed, still present, or regressed.

Learn more

LytheLabs

Try Fraser MCP.

claude mcp add fraser --env FRASER_API_KEY=your-token --env FRASER_API_URL=https://fraser.lythe.ai -- uvx --from fraser-gate@latest fraser-gate-mcp

Needs an API key and uvx.