A
licenseNot graded
qualityD
maintenanceMCP server for browser automation with AI agents, enabling network payload capture and QA workflows.
1
Apache 2.0
playwright-min-network-mcp
by bun913
Related Servers
Alternatives to playwright-min-network-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceMCP server that drives a headless or interactive Playwright browser and records every HTTP request/response into a shared web-archive store, making captured traffic searchable.-
- AlicenseNot gradedqualityCmaintenanceCaptures browser network traffic, analyzes API patterns, and exposes analysis tools through an MCP server for AI-assisted workflows.1MIT
- AlicenseBqualityDmaintenanceA universal browser automation MCP server using Playwright, enabling programmatic control of Chrome with 63 tools for navigation, interaction, media control, and CDP-based diagnostics.6313 npm2MIT
- AlicenseBqualityCmaintenance🚀 Active Fork of executeautomation/mcp-playwright This repository is an actively maintained continuation of the original MCP Playwright server: >👉 https://github.com/executeautomation/mcp-playwright A Model Context Protocol server that provides browser automation capabilities using Playwright.6327,948 npm1MIT
- AlicenseNot gradedqualityDmaintenanceA comprehensive browser automation MCP server using Playwright, offering 50+ tools for page control, element interaction, content extraction, and more across multiple browser engines.13 npm1MIT
TDQS
A4/5.0
Scored across 5 tools
Disambiguation5/5
Each tool has a distinct role: start_monitor initiates, update_filter configures, get_recent_requests and get_request_detail serve different retrieval needs (compact vs. detailed by UUID), and stop_monitor terminates. Even the two retrieval tools are clearly separated by preview length and lookup method.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern: start_monitor, update_filter, stop_monitor, get_request_detail, get_recent_requests. The verbs are clear and the naming is uniform.
Tool Count5/5
Five tools is exactly the right scope for a network monitoring MCP. Each tool covers a necessary part of the workflow without redundancy or bloat.
Completeness4/5
The tool set covers the full monitor lifecycle: start, configure, query, and stop. Missing features like clearing logs or exporting data are minor and don't create dead ends for the primary use case.
Maintenance
ActivityInactive
ResponsivenessNo issues