Test results for "MCP"

5405 passed, 172 skipped

Merge workflow run.

Test results for "tests 1"

38691 passed, 846 skipped

Merge workflow run.

Great work on adding filtering and request headers/body support! This will be very useful for debugging network issues.

I'd like to suggest adding a complementary tool: browser_get_network_response to retrieve response bodies by request ID.

Use Case

Currently, browser_network_requests shows request metadata (URL, method, headers, payload), but to inspect the actual response body, users need to write custom code with page.on('response'). A dedicated tool would streamline this workflow.

Proposed API

browser_get_network_response: {
  request_id: string;  // From browser_network_requests output
}

Example Workflow

# 1. List requests
browser_network_requests
# Output: [req_123] [GET] https://api.example.com/data

# 2. Get response body
browser_get_network_response: { request_id: "req_123" }
# Output: {"status": "success", "data": [...]}

Implementation Notes

• Auto-detects content type (JSON, text, images)
• Truncates large responses (configurable limit)
• Handles binary content (images as base64 or direct display)
• Gracefully handles collected responses (memory optimization)

Question

Would this fit within the scope of this PR, or should it be a separate contribution? I have a working implementation if you're interested.

Thanks for driving these improvements to the network tools!