Dynamic network chaos in Playwright: 503s, latency, mid-flight drops
Playwright MCP server exists for a simple reason — assistants are far more useful when they can act on Playwright directly instead of describing what you should do. Dynamic network chaos in Playwright: 503s, latency, mid-flight drops.
An MCP server that gives AI agents dynamic network chaos control over Playwright browser sessions.
Once Playwright is connected, these are the calls the assistant has available:
simulate_api_failure — Intercepts requests matching a pattern and forces them to return an error status code. Checks if the app shows a fallback UIinject_latency — Adds artificial delay to matching requests. Checks if loading states appear while the app waitsblock_resources — Aborts requests to specified URL patterns — for testing third-party outages (analytics, CDNs, tracking pixels)simulate_network_drop — Aborts requests mid-flight after a delay — simulating connection loss between request and responsetrigger_system_network_error — Aborts requests with an OS-level error code — simulating DNS failures, firewall blocks, and connection resetssimulate_stateful_failure — Fails the first N requests then lets subsequent ones succeed — testing retry logic and recovery flowsinject_response_corruption — Serves malformed responses at the protocol level — unterminated JSON, content-length lies, or truncated payloadsassert_chaos_handled — Injects a chaos HTTP status and returns a structured pass/fail verdict — chaos_survived is true only when the fallback UI appears and there are noplaywright-network-chaos-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Playwright's toolset — simulate_api_failure, inject_latency, block_resources and 5 more — is a fair guide to whether it matches your workflow.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| simulate_api_failure | Intercepts requests matching a pattern and forces them to return an error status code. Checks if the app shows a fallback UI. |
| inject_latency | Adds artificial delay to matching requests. Checks if loading states appear while the app waits. |
| block_resources | Aborts requests to specified URL patterns — for testing third-party outages (analytics, CDNs, tracking pixels). |
| simulate_network_drop | Aborts requests mid-flight after a delay — simulating connection loss between request and response. |
| trigger_system_network_error | Aborts requests with an OS-level error code — simulating DNS failures, firewall blocks, and connection resets. |
| simulate_stateful_failure | Fails the first N requests then lets subsequent ones succeed — testing retry logic and recovery flows. |
| inject_response_corruption | Serves malformed responses at the protocol level — unterminated JSON, content-length lies, or truncated payloads. |
| assert_chaos_handled | Injects a chaos HTTP status and returns a structured pass/fail verdict — chaos_survived is true only when the fallback UI appears and there are no unhandled JS exceptions. |
{
"mcpServers": {
"playwright-network-chaos-mcp": {
"command": "npx",
"args": ["-y", "playwright-network-chaos-mcp"]
}
}
}Configuration as documented by the project. Restart the client after saving.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.