Playwright Network Chaos MCP

MCP server that gives AI agents dynamic network chaos control over Playwright browser sessions

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "playwright-network-chaos-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "playwright-network-chaos-mcp"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

playwright-network-chaos-mcp 🐸💥

An MCP server that gives AI agents dynamic network chaos control over Playwright browser sessions.

Your tests run on perfect networks. Your users don't. This MCP lets AI agents simulate API outages, inject latency, drop connections mid-flight, and block third-party resources — then assert whether the app handles it gracefully.

🤔 The Problem

CI environments have flawless connectivity. APIs respond in milliseconds. CDNs never go down. So your tests pass — and then production breaks when the payment service returns a 503, the network drops mid-checkout, or Google Analytics hangs for 8 seconds and freezes the page.

AI agents writing Playwright tests have no way to introduce or reason about network instability. They can't ask:

🙈 Does the checkout page show an error state when the payment API fails?
🙈 Does the skeleton loader appear while the dashboard API is slow?
🙈 Does the app still work if all tracking scripts are blocked?
🙈 What happens if the network drops after the order is submitted but before the response arrives?

playwright-network-chaos-mcp fixes that.

🛠️ Tools

`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.

config.json

{
  "url": "https://your-app.com/checkout",
  "intercept_pattern": "**/api/payment**",
  "status_code": 503,
  "fallback_selector": ".error-boundary",
  "wait_ms": 2000
}

config.json

{
  "intercepted_count": 2,
  "fallback_found": true,
  "fallback_selector": ".error-boundary",
  "page_state": {
    "page_errors": [],
    "console_errors": ["Failed to load resource: 503"]
  }
}

`inject_latency`

Adds artificial delay to matching requests. Checks if loading states appear while the app waits.

config.json

{
  "url": "https://your-app.com/dashboard",
  "intercept_pattern": "**/api/**",
  "latency_ms": 3000,
  "jitter_ms": 500,
  "loading_selector": ".skeleton-loader"
}

config.json

{
  "intercepted_count": 4,
  "intercepted_requests": [
    { "url": "https://api.your-app.com/users", "method": "GET", "delay_ms": 3241 }
  ],
  "loading_state_found": true,
  "load_time_ms": 3890
}

`block_resources`

Aborts requests to specified URL patterns — for testing third-party outages (analytics, CDNs, tracking pixels).

config.json

{
  "url": "https://your-app.com",
  "block_patterns": ["**/analytics**", "*.doubleclick.net/**", "**/hotjar**"],
  "core_content_selector": ".main-content",
  "wait_ms": 2000
}

config.json

{
  "blocked_count": 7,
  "blocked_urls": ["https://www.google-analytics.com/analytics.js", "..."],
  "core_content_found": true,
  "page_state": { "page_errors": [], "console_errors": [] }
}

`simulate_network_drop`

Aborts requests mid-flight after a delay — simulating connection loss between request and response.

config.json

{
  "url": "https://your-app.com/checkout",
  "intercept_pattern": "**/api/order**",
  "drop_after_ms": 800,
  "fallback_selector": ".network-error-toast",
  "wait_ms": 3000
}

config.json

{
  "intercepted_count": 1,
  "fallback_found": true,
  "fallback_selector": ".network-error-toast",
  "page_state": { "page_errors": ["TypeError: Failed to fetch"] }
}

`trigger_system_network_error`

Aborts requests with an OS-level error code — simulating DNS failures, firewall blocks, and connection resets.

config.json

{
  "url": "https://your-app.com/dashboard",
  "intercept_pattern": "**/api/**",
  "error_code": "addressunreachable",
  "fallback_selector": ".network-error"
}

config.json

{
  "error_code": "addressunreachable",
  "intercepted_count": 3,
  "fallback_found": true,
  "page_state": { "page_errors": [], "console_errors": ["net::ERR_ADDRESS_UNREACHABLE"] }
}

`simulate_stateful_failure`

Fails the first N requests then lets subsequent ones succeed — testing retry logic and recovery flows.

config.json

{
  "url": "https://your-app.com/dashboard",
  "intercept_pattern": "**/api/data**",
  "http_status": 503,
  "failure_count": 2,
  "success_payload": "{\"data\":[]}",
  "fallback_selector": ".retry-button"
}

config.json

{
  "failure_count": 2,
  "actual_failed": 2,
  "actual_succeeded": 1,
  "intercepted_requests": [
    { "url": "...", "method": "GET", "status": 503, "attempt": 1, "outcome": "failed" },
    { "url": "...", "method": "GET", "status": 200, "attempt": 3, "outcome": "passed" }
  ],
  "fallback_found": true
}

`inject_response_corruption`

Serves malformed responses at the protocol level — unterminated JSON, content-length lies, or truncated payloads.

config.json

{
  "url": "https://your-app.com/checkout",
  "intercept_pattern": "**/api/order**",
  "corruption_type": "malformed_json",
  "fallback_selector": ".parse-error"
}

config.json

{
  "corruption_type": "malformed_json",
  "intercepted_count": 1,
  "fallback_found": false,
  "page_state": { "page_errors": ["SyntaxError: Unexpected token u in JSON"] }
}

`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.

config.json

{
  "url": "https://your-app.com/checkout",
  "intercept_pattern": "**/api/**",
  "http_status": 500,
  "expected_fallback_selector": ".error-boundary"
}

config.json

{
  "http_status": 500,
  "unhandled_exceptions": [],
  "console_errors": ["Failed to load resource: 500"],
  "fallback_ui_detected": true,
  "chaos_survived": true
}

🚀 Installation

Terminal

npx playwright-network-chaos-mcp

Or install globally:

Terminal

npm install -g playwright-network-chaos-mcp
npx playwright install chromium

Claude Desktop config

config.json

{
  "mcpServers": {
    "playwright-network-chaos-mcp": {
      "command": "npx",
      "args": ["-y", "playwright-network-chaos-mcp"]
    }
  }
}

💡 Example Agent Prompts

"Check if the checkout page shows a proper error state when the payment API returns 503"

"Simulate a 3 second API delay on the dashboard and verify the skeleton loader appears"

"Block all analytics and tracking scripts and confirm the main content still loads"

"Drop the order submission request mid-flight and check if the user sees an error message"

"Simulate DNS failure for the API and check if the error boundary renders"

"Fail the first 3 requests then succeed — does the app retry and recover automatically?"

"Inject malformed JSON and assert the app doesn't crash — return a chaos verdict"

🔗 Related Projects

playwright-trace-decoder-mcp — root-cause analysis of CI failures from Playwright traces
flakiness-knowledge-graph-mcp — knowledge graph of flaky test patterns
ast-impact-mapper-mcp — find affected tests from code changes via TypeScript AST
zod-contract-mock-forge-mcp — deterministic mock generation from Zod schemas
playwright-spatial-layout-mcp — geometric spatial awareness of web layouts

📄 License

MIT © vola-trebla

Read the full README →View source on GitHub →

Related MCP Servers

View all in Browser Automation View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Playwright Network Chaos MCP

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "playwright-network-chaos-mcp": { "command": "npx", "args": ["-y", "playwright-network-chaos-mcp"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Playwright Network Chaos MCP AllMCPs Directory Badge

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/playwright-network-chaos-mcp?style=directory)](https://allmcps.com/mcp/playwright-network-chaos-mcp)

HTML Embed

<a href="https://allmcps.com/mcp/playwright-network-chaos-mcp"><img src="https://allmcps.com/api/badge/playwright-network-chaos-mcp?style=directory" alt="Playwright Network Chaos MCP on AllMCPs" /></a>

Technical Specs & Signals

CategoryBrowser Automation

27Quality signal: Emerging · 27/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership8/20

Documentation & tools11/30

Adoption & activity1/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

★ Spotlight Slot

Feature Your MCP Server

Get maximum visibility for your server across our directory, search results, and detail pages.

Spotlight Your Server

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge and attach your website — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 📂 Browser Automation →Best MCP servers for Browser Automation →Alternatives to Playwright Network Chaos MCP →Install in Claude Desktop Install in Cursor Install in VS Code

Playwright Network Chaos MCP

MCP server that gives AI agents dynamic network chaos control over Playwright browser sessions

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "playwright-network-chaos-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "playwright-network-chaos-mcp"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

playwright-network-chaos-mcp 🐸💥

An MCP server that gives AI agents dynamic network chaos control over Playwright browser sessions.

🤔 The Problem

AI agents writing Playwright tests have no way to introduce or reason about network instability. They can't ask:

🙈 Does the checkout page show an error state when the payment API fails?
🙈 Does the skeleton loader appear while the dashboard API is slow?
🙈 Does the app still work if all tracking scripts are blocked?
🙈 What happens if the network drops after the order is submitted but before the response arrives?

playwright-network-chaos-mcp fixes that.

🛠️ Tools

`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.

config.json

{
  "url": "https://your-app.com/checkout",
  "intercept_pattern": "**/api/payment**",
  "status_code": 503,
  "fallback_selector": ".error-boundary",
  "wait_ms": 2000
}

config.json

{
  "intercepted_count": 2,
  "fallback_found": true,
  "fallback_selector": ".error-boundary",
  "page_state": {
    "page_errors": [],
    "console_errors": ["Failed to load resource: 503"]
  }
}

`inject_latency`

Adds artificial delay to matching requests. Checks if loading states appear while the app waits.

config.json

{
  "url": "https://your-app.com/dashboard",
  "intercept_pattern": "**/api/**",
  "latency_ms": 3000,
  "jitter_ms": 500,
  "loading_selector": ".skeleton-loader"
}

config.json

{
  "intercepted_count": 4,
  "intercepted_requests": [
    { "url": "https://api.your-app.com/users", "method": "GET", "delay_ms": 3241 }
  ],
  "loading_state_found": true,
  "load_time_ms": 3890
}

`block_resources`

Aborts requests to specified URL patterns — for testing third-party outages (analytics, CDNs, tracking pixels).

config.json

{
  "url": "https://your-app.com",
  "block_patterns": ["**/analytics**", "*.doubleclick.net/**", "**/hotjar**"],
  "core_content_selector": ".main-content",
  "wait_ms": 2000
}

config.json

{
  "blocked_count": 7,
  "blocked_urls": ["https://www.google-analytics.com/analytics.js", "..."],
  "core_content_found": true,
  "page_state": { "page_errors": [], "console_errors": [] }
}

`simulate_network_drop`

Aborts requests mid-flight after a delay — simulating connection loss between request and response.

config.json

{
  "url": "https://your-app.com/checkout",
  "intercept_pattern": "**/api/order**",
  "drop_after_ms": 800,
  "fallback_selector": ".network-error-toast",
  "wait_ms": 3000
}

config.json

{
  "intercepted_count": 1,
  "fallback_found": true,
  "fallback_selector": ".network-error-toast",
  "page_state": { "page_errors": ["TypeError: Failed to fetch"] }
}

`trigger_system_network_error`

Aborts requests with an OS-level error code — simulating DNS failures, firewall blocks, and connection resets.

config.json

{
  "url": "https://your-app.com/dashboard",
  "intercept_pattern": "**/api/**",
  "error_code": "addressunreachable",
  "fallback_selector": ".network-error"
}

config.json

{
  "error_code": "addressunreachable",
  "intercepted_count": 3,
  "fallback_found": true,
  "page_state": { "page_errors": [], "console_errors": ["net::ERR_ADDRESS_UNREACHABLE"] }
}

`simulate_stateful_failure`

Fails the first N requests then lets subsequent ones succeed — testing retry logic and recovery flows.

config.json

{
  "url": "https://your-app.com/dashboard",
  "intercept_pattern": "**/api/data**",
  "http_status": 503,
  "failure_count": 2,
  "success_payload": "{\"data\":[]}",
  "fallback_selector": ".retry-button"
}

config.json

{
  "failure_count": 2,
  "actual_failed": 2,
  "actual_succeeded": 1,
  "intercepted_requests": [
    { "url": "...", "method": "GET", "status": 503, "attempt": 1, "outcome": "failed" },
    { "url": "...", "method": "GET", "status": 200, "attempt": 3, "outcome": "passed" }
  ],
  "fallback_found": true
}

`inject_response_corruption`

Serves malformed responses at the protocol level — unterminated JSON, content-length lies, or truncated payloads.

config.json

{
  "url": "https://your-app.com/checkout",
  "intercept_pattern": "**/api/order**",
  "corruption_type": "malformed_json",
  "fallback_selector": ".parse-error"
}

config.json

{
  "corruption_type": "malformed_json",
  "intercepted_count": 1,
  "fallback_found": false,
  "page_state": { "page_errors": ["SyntaxError: Unexpected token u in JSON"] }
}

`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.

config.json

{
  "url": "https://your-app.com/checkout",
  "intercept_pattern": "**/api/**",
  "http_status": 500,
  "expected_fallback_selector": ".error-boundary"
}

config.json

{
  "http_status": 500,
  "unhandled_exceptions": [],
  "console_errors": ["Failed to load resource: 500"],
  "fallback_ui_detected": true,
  "chaos_survived": true
}

🚀 Installation

Terminal

npx playwright-network-chaos-mcp

Or install globally:

Terminal

npm install -g playwright-network-chaos-mcp
npx playwright install chromium

Claude Desktop config

config.json

{
  "mcpServers": {
    "playwright-network-chaos-mcp": {
      "command": "npx",
      "args": ["-y", "playwright-network-chaos-mcp"]
    }
  }
}

💡 Example Agent Prompts

"Check if the checkout page shows a proper error state when the payment API returns 503"

"Simulate a 3 second API delay on the dashboard and verify the skeleton loader appears"

"Block all analytics and tracking scripts and confirm the main content still loads"

"Drop the order submission request mid-flight and check if the user sees an error message"

"Simulate DNS failure for the API and check if the error boundary renders"

"Fail the first 3 requests then succeed — does the app retry and recover automatically?"

"Inject malformed JSON and assert the app doesn't crash — return a chaos verdict"

🔗 Related Projects

playwright-trace-decoder-mcp — root-cause analysis of CI failures from Playwright traces
flakiness-knowledge-graph-mcp — knowledge graph of flaky test patterns
ast-impact-mapper-mcp — find affected tests from code changes via TypeScript AST
zod-contract-mock-forge-mcp — deterministic mock generation from Zod schemas
playwright-spatial-layout-mcp — geometric spatial awareness of web layouts

📄 License

Read the full README →View source on GitHub →

Related MCP Servers

View all in Browser Automation View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Playwright Network Chaos MCP

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "playwright-network-chaos-mcp": { "command": "npx", "args": ["-y", "playwright-network-chaos-mcp"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/playwright-network-chaos-mcp?style=directory)](https://allmcps.com/mcp/playwright-network-chaos-mcp)

HTML Embed

<a href="https://allmcps.com/mcp/playwright-network-chaos-mcp"><img src="https://allmcps.com/api/badge/playwright-network-chaos-mcp?style=directory" alt="Playwright Network Chaos MCP on AllMCPs" /></a>

Technical Specs & Signals

CategoryBrowser Automation

27Quality signal: Emerging · 27/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership8/20

Documentation & tools11/30

Adoption & activity1/15

Community engagement0/10

★ Spotlight Slot

Feature Your MCP Server

Get maximum visibility for your server across our directory, search results, and detail pages.

Spotlight Your Server

Own this project?

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 📂 Browser Automation →Best MCP servers for Browser Automation →Alternatives to Playwright Network Chaos MCP →Install in Claude Desktop Install in Cursor Install in VS Code