muggle

muggle-ai-works

Run real-browser E2E acceptance tests on your web app from any AI coding agent. Generate test scripts from plain English, replay them on localhost, capture screenshots, and validate user flows like signup, checkout, and dashboards. Works across Claude Code, Cursor, Codex, and Windsurf.

One install gives your AI coding assistant the power to exercise your app like a real user would: clicking through flows, catching broken experiences, and reporting results with screenshots and evidence.

*License: MIT npm MCP Tools Node*

Powered by MuggleTest — the AI-powered E2E acceptance testing platform.

---

Why muggle-ai-works?

Your AI assistant writes code fast. But does the feature actually work? Does the login flow break on mobile? Does the checkout still render after that refactor?

muggle-ai-works closes the gap between "code complete" and "actually works."

• Catch UX regressions before your users do — AI drives a real browser against your localhost across desktop and mobile resolutions, clicks through flows like a user would, and reports failures with step-by-step screenshots. No Playwright scripts to maintain.
• Go from requirement to merged PR in one command — /muggle:muggle-do handles the full cycle: code the feature, run unit tests, run E2E acceptance tests against the app in a real browser at multiple viewports, triage failures, and open a PR with evidence attached.
• 70+ MCP tools for custom workflows — manage projects, generate test cases from plain English, replay test scripts, batch-run regressions, and publish results to your team. Works in Claude Code, Cursor, and any MCP client.

---

Quick Start

1. Install (choose your client)

Claude Code (full plugin experience)

/plugin marketplace add https://github.com/multiplex-ai/muggle-ai-works
/plugin install muggleai@muggle-works

This installs:

• /muggle:muggle — command router and menu
• /muggle:muggle-do — autonomous dev pipeline (requirements to PR)
• /muggle:muggle-test — change-driven E2E acceptance testing (local or remote, with PR posting)
• /muggle:muggle-test-feature-local — local quick E2E acceptance testing
• /muggle:muggle-status — health check for muggle-works plugins (Electron app, MCP server, and auth)
• /muggle:muggle-repair — diagnose and fix broken installation
• /muggle:muggle-upgrade — update to the latest version
• MCP server with 70+ tools (auto-started)
• Electron browser test runner provisioning (via session hook)

Cursor, Codex, Windsurf, and other MCP clients (MCP tools only)

npm install -g @muggleai/works

Then configure your MCP client:

{
  "mcpServers": {
    "muggle": {
      "command": "muggle",
      "args": ["serve"],
      "env": {
        "MUGGLE_MCP_PROMPT_SERVICE_TARGET": "production"
      }
    }
  }
}

npm install also syncs muggle-* skills to ~/.cursor/skills/ for Cursor discovery. Claude slash commands are plugin-managed, so update those with /plugin update muggleai@muggle-works.

2. Verify

Claude Code

/muggle:muggle-status

This checks Electron browser test runner, MCP server health, and authentication. If anything is broken, run /muggle:muggle-repair.

Cursor/Codex/Windsurf/other MCP clients

Run any muggle-* MCP tool from your client after adding the MCP server config above. Authentication starts automatically on first protected tool call.

3. Start building features

Claude Code

Describe what you want to build:

/muggle:muggle-do "Add a logout button to the header"

The AI handles the full cycle: code the feature, run unit tests, run E2E acceptance tests against the app in a real browser, and open a PR with results.

Cursor/Codex/Windsurf/other MCP clients

Use the direct MCP workflow section below to call muggle-* tools from your client.

4. Test a feature locally

Claude Code

Already have code running on localhost? Test it directly:

/muggle:muggle-test-feature-local

Describe what to test in plain English. The AI finds or creates test cases, launches a real browser, and reports results with screenshots.

Cursor/Codex/Windsurf/other MCP clients

Call local execution MCP tools directly (for example muggle-local-execute-test-script-replay or related muggle-local-* commands exposed by your client).

---

How does it work?

muggle-ai-works separates test management from test execution. All entity management (projects, use cases, test cases) lives in the cloud via muggle-remote-* tools. Local execution (muggle-local-*) is stateless — it receives what it needs and runs the test.

Entity model