Diagnose rendering issues and JavaScript errors in web apps by capturing a screenshot and browser console logs.
BSD 3-Clause
466,320 tools. Updated 2026-08-19 13:13
"Browser Debug Tool for Capturing Console Errors and Taking Screenshots" matching MCP tools:
- Start capturing browser console logs (console.log, console.error, console.warn) to monitor JavaScript output and debug web applications during automated browser sessions.MIT
- Debug a webpage by capturing console output, network requests, errors, and layout thrashing with custom device emulation and adjustable output limits.MIT
- Capture browser console logs including errors and warnings to debug JavaScript issues during test automation.
- Monitor browser console logs to detect errors and debug output by capturing specified log levels from a URL for a set duration.MIT
- Retrieve captured browser console logs with filters for level, content, and time, to quickly identify errors and debug output without altering the page.MIT
Matching MCP Servers
- Alicense-qualityAmaintenanceA Playwright-based browser automation tool for AI agents, enabling web search, navigation, scraping, and page interaction through the Model Context Protocol.MIT
- FlicenseAqualityCmaintenanceGives Claude control of a real, headed Chromium browser via Playwright, enabling web navigation, clicking, typing, screenshots, and JavaScript evaluation.8
Matching MCP Connectors
The official MCP Server from Mia-Platform to interact with Mia-Platform Console
Hosted real Google Chrome MCP with per-user persistent state. Navigate, click, type, screenshot.
- Pull user debug feedback records for the selected app, download screenshots and logs, and generate AI-ready debug context files.MIT
- Adds an on-screen debug logger to display logs, warnings, and errors on mobile devices. Useful for H5 games and non-technical testers to view console output without a developer console.MIT
- Retrieve browser console logs from Webvizio tasks when the task prompt lacks sufficient information for execution, providing additional context to complete development tasks.MIT
- Clear buffered console messages for a browser automation session to remove stale entries before capturing fresh logs.MIT
- Resize the active web browser area before capturing screenshots. Adjust width and height in CSS pixels to expose content that fixed-layout or full-height pages would otherwise hide.MIT
- Retrieve console messages from automated browser sessions to monitor errors, warnings, and debug information during web testing and automation tasks.
- Guides setup and use of agent-browser CLI for automated browser tasks like navigating pages, clicking, and capturing console errors in a real browser.MIT
- Retrieve console logs from any browser tab to debug errors and monitor client-side activity. Specify a tab ID or use the active tab.MIT
- Execute JavaScript code in a browser console to automate web interactions, extract data, or modify page content using browser automation capabilities.MIT
- Starts capturing console output on the current page, enabling retrieval of console messages. Call it before using list_console_messages or get_console_message.MIT
- Close the BrightScript debug console on a Roku device to release the debug port and stop log accumulation.MIT
- Extract specific failing network, console, mutation, interaction, or navigation events from a recorded browser session using category filters to surgically isolate errors without overwhelming your context.MIT
- Fetch console log messages from the browser frontend to debug JavaScript errors, with optional filters for level, text, or regex.GPL 3.0
- Inspect a local web page by capturing a screenshot, console errors, and a DOM snapshot with CSS classes to debug layout, responsive breakpoints, and hydration issues.MIT