815,459 tools. Updated 2026-11-21 09:19
"Understanding and Using the Browser Console" matching MCP tools:
- 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
- Close the browser and wipe all session state—tabs, references, and console logs—to start fresh. For CDP connections, detach without terminating the browser.MIT
- Retrieve console log messages from browser tabs to monitor errors, warnings, and debug information during web application testing and development.MIT
- Read browser console logs and filter them by level or regex pattern, with an option to clear the buffer after reading.MIT
- Retrieve browser console logs or evaluate JavaScript expressions to debug and interact with web pages.MIT
Matching MCP Servers
- AlicenseNot gradedqualityBmaintenanceMCP server for multimodal understanding and object grounding (bounding boxes) across images, videos, and documents, with support for multiple AI providers (Zhipu GLM-V, OpenAI GPT-4o, Anthropic Claude, or any OpenAI-compatible endpoint).1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to maintain persistent, inspectable understanding through typed, revisable updates, and to coordinate multi-agent work via shared graph-based stigmergy.141 npm1MIT
Matching MCP Connectors
A real Chromium browser agents can pay for per action over x402 (USDC on Base): navigate $0.005, extract $0.005, accessibility snapshot $0.005, act $0.01, screenshot $0.02, close free. Also runs free self-hosted over stdio via npx @scriptmasterlabs/agent-browser. Six tools with structured error codes and a public receipts log. Source: https://gitlab.com/timothy.walton45/agent-browser
Browser agents and stealth cloud browsers for AI: run web tasks, fill forms, extract data.
- Retrieve browser console messages from a specific tab, filter with a regex pattern, and debug JavaScript errors or review application logs without noise.Apache 2.0
- Diagnose rendering issues and JavaScript errors in web apps by capturing a screenshot and browser console logs.BSD 3-Clause
- Close the Google Search Console browser session when work is done to stop credit usage.Elastic 2.0
- Retrieve recent browser console messages and page errors to correlate visual issues with JavaScript errors.MIT
- Capture and review browser console logs for any tab. Start monitoring to collect messages, filter by level, list entries, or clear the buffer for debugging.MIT
- Start the Google OAuth 2.0 browser flow to authorize access to Meet, Drive, and Calendar, using credentials.json from Google Cloud Console.MIT
- Retrieve the last 500 browser console entries from a specific tab, with optional filtering by console level and incremental polling using a timestamp cursor.MIT
- Retrieve browser console logs to debug JavaScript errors, warnings, and other messages during automated browser sessions.ISC
- Retrieve browser console logs to debug JavaScript errors and monitor runtime activity. Access log entries directly for troubleshooting web pages.Apache 2.0
- Fetch browser console logs to diagnose JavaScript errors and identify web application issues.Apache 2.0
- Open the local Search Console dashboard in your browser to review performance, queries, pages, opportunities, and indexing data.MIT
- Diagnose errors from terminal, console, browser, or build failure screenshots. Extract the error message and provide actionable insights for resolution.MIT
- Fetch browser console error messages with stack traces to diagnose and fix web app issues.MIT
- Capture and filter browser console output to diagnose JavaScript errors, warnings, uncaught exceptions, and messages during web inspection.MIT
- Capture browser console output by navigating to a URL, with options for real-time streaming, wait conditions, and custom browser commands.MIT