Mimiq MCP server: user testing from your coding agent

Coding agents ship pages and signup flows in minutes, and nobody outside the team sees them until real visitors do. A test inside the coding agent's loop puts simulated visitors in front of the change while it is still cheap to fix, and the coding agent can read what they hit and act on it before you review the diff.

• Two tools: test_flow and show_report.
• Works with Claude Code, Codex, Cursor, VS Code, Windsurf, and Claude Desktop.
• One free test without a key; a free account adds 50 credits.
• With a key, runs are saved to your account, with a link to the full report.

In Claude Code, run this once in your project. Leave out the header to use the free test, or set MIMIQ_API_KEY to a key from your Mimiq settings.

claude mcp add --transport http mimiq https://mcp.mimiqai.com/mcp --header "Authorization: Bearer $MIMIQ_API_KEY"

Clients that read an MCP config file take the same address. In Cursor, put this in .cursor/mcp.json, and keep a file with a key out of your repository. The README at github.com/victorgulchenko/mimiq-mcp has the setup for Codex, VS Code, Windsurf, and Claude Desktop.

{
  "mcpServers": {
    "mimiq": {
      "url": "https://mcp.mimiqai.com/mcp",
      "headers": { "Authorization": "Bearer mq_sk_..." }
    }
  }
}

Ask in plain words: have three visitors sign up on my preview deployment, or check the new checkout before I merge. Your coding agent picks the tool.

test_flow sends simulated visitors through a task in plain words on a preview or live URL, each in its own real browser, and returns each visitor's steps, what was broken, where it stopped and why, and what the browser recorded: relevant JavaScript errors, failed requests and requests slower than 3 seconds, ranked by how many visitors hit them. It uses 5 credits a visitor; without a key, a free run has up to 3 visitors, within a daily limit.

show_report reads a saved report again and uses no credits. To check a fix, run test_flow again on the new build.

Add these lines to your project's CLAUDE.md or AGENTS.md, and your coding agent checks a customer facing change before it calls it done. A short, specific rule like this is easier for an agent to follow than a long overview.

## Before calling a user facing change done
After changing anything a user goes through (signup, onboarding, checkout,
settings, a new feature), run mimiq.test_flow on the preview URL with the task
a user would try. Fix what the visitors hit, then run it again. Ask me before
using more than 25 credits.

The Mimiq preview check GitHub Action runs the same test on each preview deploy from Vercel, Netlify or Cloudflare Pages, or on any URL you give it, and keeps one comment on the pull request up to date: how many visitors finished, where the rest got stuck, and a link to the full report. Setup is one workflow file and your key as a repository secret: github.com/victorgulchenko/mimiq-preview-check.

on: deployment_status
permissions:
  pull-requests: write
jobs:
  mimiq:
    if: github.event.deployment_status.state == 'success'
    runs-on: ubuntu-latest
    steps:
      - uses: victorgulchenko/mimiq-preview-check@v1
        with:
          api-key: ${{ secrets.MIMIQ_API_KEY }}
          goal: Sign up and reach the dashboard

With paid credits, visitors can sign in with a test account you give them and open protected previews (a Vercel bypass secret or a site password). The secrets are filled in only in the browser and deleted when the run ends. Test accounts and protected previews come with paid credits: the $9 Starter or a plan from $19 a month.

Every visitor in a Mimiq result is simulated. They find problems fast: what was broken, what did nothing, where they stopped and why, each with the step and a screenshot. They do not predict how many real people will convert.

So treat a clean run as meaning nothing obvious was broken for those visitors, not as proof that the change works for everyone.

Mimiq opens pages in a real browser on its side, so the address has to be reachable from the internet. For a local dev server, open a temporary tunnel, such as a free cloudflared tunnel, and pass its address. The page is public while the tunnel runs, so your coding agent should tell you before it opens one.

To get a key, create a free account (it adds 50 credits), open Settings, find "Use Mimiq from your coding agent", and choose "Create a key". Send it as "Authorization: Bearer mq_sk_..." on every request. Then it is a $9 Starter (120 credits that never expire) or monthly plans from $19.