crowd-test-mcp 🔥
The mob, on tap — an MCP server for crowd-test.
Ask Claude Desktop, Claude Code, Cursor, or any MCP client to unleash a crowd of AI virtual users — impatient shoppers, confused seniors, keyboard-only users, chaos monkeys — on your website. They browse it in real Chromium, file findings, and hand back a damage report with a survival grade (S–F).
"Send the mob at https://staging.myapp.com and tell me what to fix first."
That's the whole workflow now.
Install
pip install crowd-test-mcp
An LLM key is required in the server's environment: ANTHROPIC_API_KEY or
OPENAI_API_KEY.
Claude Code
claude mcp add crowd-test -e ANTHROPIC_API_KEY=sk-... -- crowd-test-mcp
Claude Desktop / Cursor / anything MCP
{
"mcpServers": {
"crowd-test": {
"command": "crowd-test-mcp",
"env": { "ANTHROPIC_API_KEY": "sk-..." }
}
}
}
Tools
| Tool | What it does |
|---|---|
run_crowd_test |
Send the crowd at a URL. Pick personas, add a random mob, set a goal, choose the verification depth (none / detective / cross / tribunal). Returns a compact damage summary; full markdown/HTML reports land in ~/crowd-test-reports/. |
list_personas |
The ten built-in ringleaders and what each one catches. |
preview_mob |
Preview the random mob a given count/seed would generate. |
read_report |
Fetch the newest full markdown report from disk. |
The verification tribunal
Findings can be cross-examined by up to three independent harnesses before they count against the grade — a skeptical detective agent, a raw Playwright probe, and a Microsoft Webwright agent. Automation artifacts get disputed instead of panicking you. Details in the crowd-test README.
Deeper layers need one-time extras:
pip install crowd-test[probe] && playwright install chromium # verify="cross"
pip install git+https://github.com/microsoft/Webwright # verify="tribunal"
Good to know
- Runs take minutes, not seconds — every persona drives a real browser.
Start with 2–3 personas; escalate to
mob=10when you mean it. - Only test what you own. The mob is for your own staging and production sites, not other people's.
- Reports default to
~/crowd-test-reports/<host>-<timestamp>/.
License
Release files for crowd-test-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| crowd_test_mcp-0.1.0.tar.gz | 7.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| crowd_test_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 15.0 kB
Release files / crowd_test_mcp-0.1.0.tar.gz
| Download URL | crowd_test_mcp-0.1.0.tar.gz |
|---|---|
| Size | 7.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
911965b617d3ff49b183443721ac710c280814129b46fbfed3a6fcf8d4e52080
|
|
BLAKE2b-256 checksum How to use checksums |
d6c39210490a5b0faec31e63c252407d2a03cb0359d93d94e229282d08d2adf0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 23, 2026.
Transparency logRelease files / crowd_test_mcp-0.1.0-py3-none-any.whl
| Download URL | crowd_test_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 7.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ecbaef79ce5237101652aa1005b838303b64b2f44a7be5034cc7402bdcaff8d3
|
|
BLAKE2b-256 checksum How to use checksums |
b243b895724dea8ca844edda5720c0ead674c27c1b5bdd8059b934822fe1f989
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 23, 2026.
Transparency log