For Claude Code builders
Test the app Claude Code built before real users do
Claude Code wrote it in an afternoon and nobody but you has used it. Before you post it, let simulated people try to sign up on the live app: each one opens it in their own real browser and clicks, types and waits like a newcomer would, so you see where they get stuck and why.
How do I test an app built with Claude Code before launch?
Deploy it to a public address, paste the address and give simulated people a task such as signing up. Each one uses the real app in a real browser for up to 40 steps, with made-up details and an inbox of their own, and the report shows how far each one got and where they stopped, in their own words. You can also add Mimiq's MCP server to Claude Code and let the agent run the test itself.
Why an app Claude Code built can break where you can't see it
An app written by a coding agent usually works when you click through it, because you know where everything is and you are already signed in. The tests an agent writes check that the code does what the agent meant. They do not check that a stranger can find the button, read the error or understand the first screen. A newcomer arrives cold: the confirmation email lands in a different tab, an error says nothing useful, or the first screen after sign-up is empty. You usually learn that from silence after launch. A flow test shows it before.
- Simulated people use your live app in real browsers: they click, scroll, type and fill in forms.
- Each one has an email address with a working inbox, so a confirmation link or code reaches them.
- See how far each person got, step by step, and where and why they stopped, in their own words.
- Claude Code can run the test itself through the Mimiq MCP server, and read back who got stuck and why.
How it works
- 01
Deploy the app
Claude Code writes the code and does not host it, so deploy it the way you normally do. Preview deployments are often protected by a login; test the production address, or make the preview public first. The people can't log in to your account, so start from a page anyone can open, such as the homepage or the sign-up page.
- 02
Paste the address and the task
The task starts as 'Sign up and start using it'. Write your own if your app has a clear first goal, such as 'Create your first project'. Pick 1, 3, 5, 10 or 20 people: Mimiq matches them to who the app is for, or you describe them.
- 03
Watch them use it
Each person gets up to 40 steps in a real browser. You see their screens and every step as it happens.
- 04
Fix the first problem, then rerun
The report ranks the issues by how many people hit them, with a suggested fix. Hand it to Claude Code, deploy again, and run it again on the same people.
What usually goes wrong in an app Claude Code built
Apps built with a coding agent often share a shape: a generated landing page, an email or social sign-up through an auth provider, and a first screen that is empty until you add something. Each part can lose a newcomer quietly: a sign-up button that does nothing on the first click, a confirmation email that never arrives or says nothing about what to do next, a form error with no hint, or a first screen that assumes you already know the app.
A flow test finds these where they happen. Every click and form entry records whether it moved the person on, changed nothing, or failed, so a broken button or a silent error shows up as the step where people stopped.
Run it from inside Claude Code
Mimiq runs an MCP server at https://mcp.mimiqai.com/mcp. In Claude Code, run this once in your project. Leave out the header to use the one free test, or set MIMIQ_API_KEY to a key from your Mimiq settings.
Then ask Claude Code in plain words to test the deployed address: for example, 'run a sign-up flow on my production site and tell me where people got stuck'. One free test works without a key. Setup for other clients, the eight tools and how far to trust the results are on the MCP page.
claude mcp add --transport http mimiq https://mcp.mimiqai.com/mcp --header "Authorization: Bearer $MIMIQ_API_KEY"What it does not do
Simulated people are not real users. They show you where a newcomer is likely to get stuck and why, which is most useful before you have traffic. Once real people arrive, watch them too.
Anyone stopped by one is marked as blocked by the site, and if it stops everyone, the flow fails and nothing is charged. A staging or preview address without bot protection works, as long as it is public.
Questions
Does it work with any app Claude Code built?
Any app with a public address. If it sits behind a login or a password page, the simulated people stop there, because they can't use your account.
Can they really sign up?
Yes. They fill in your forms with made-up details from their profile and an email address of their own on a Mimiq domain. That inbox works, so confirmation links and codes reach them.
Will this create fake accounts in my app?
Yes, one per person who gets through sign-up, with a Mimiq email address. Delete them afterwards, or test on a staging copy of the app.
Can Claude Code run the test itself?
Yes, through Mimiq's MCP server at https://mcp.mimiqai.com/mcp. Your agent sends the address and the task, and gets back who got through, where each person stopped and why. One free test works without a key.
What does it cost?
Your first test is free with a free account: sign in with Google and it starts right away, no card. The account includes 50 credits, enough for 10 people in a flow. After that a flow uses 5 credits a person, and then it is a $9 Starter (120 credits that never expire) or monthly plans from $49.
Keep reading
Find the step that loses people.
Your first test is free: sign in with Google and it starts right away. Last checked 2026-10-08.