"How to access browser console for debugging and error rectification" matching MCP servers:

Enables LLMs to automatically diagnose coding errors through codebase search, test execution, and live debugger integration (DAP/V8 CDP). Provides a secure, policy-gated environment for investigating failures while preventing destructive operations.

Enables LLM agents to search and analyze Elasticsearch logs for errors, detect recurring patterns, analyze error-rate trends, and retrieve full trace context through MCP tools.

Controls a running Chrome/Chromium browser via the Chrome DevTools Protocol, enabling navigation, JavaScript evaluation, tab management, and raw CDP commands through MCP tools.

MCP server that exposes GDB debugging as tools. An AI assistant can set breakpoints, run programs, step through code, inspect variables and memory, and examine registers — all via structured tool calls. Reverse debugging with rr is also supported.

A read-only MCP server for Google Search Console that lets you query search performance data, sitemaps, and URL index status from any MCP client.

Multi-account Google Search Console MCP server enabling AI assistants to query multiple GSC accounts by name in a single session, with support for OAuth and service accounts.

Model Context Protocol (MCP) server that provides AI agents with access to Google Search Console data.

Converts AI Skills (following Claude Skills format) into MCP server resources, enabling LLM applications to discover, access, and utilize self-contained skill directories through the Model Context Protocol. Provides tools to list available skills, retrieve skill details and content, and read supporting files with security protections.

MCP server for Google Search Console API, enabling search performance analysis, URL inspection, sitemap management, and property listing. Supports local, self-hosted, and Cloudflare Workers deployments.

Relays a result screenshot to Slack so you can review a coding agent's output without opening the app.

Browser-based research MCP server that drives a real Chromium browser via patched Playwright to access JavaScript-rendered content, dynamic tables, and login-walled dashboards. It provides tools for visiting URLs to extract DOM text and screenshots, and for performing structured data extraction using Anthropic Claude Sonnet.

Exposes Adobe's User Management API (UMAPI) as MCP tools for listing users, managing product profiles, and assigning or removing Acrobat/PDF licenses in Enterprise organizations.

Downloads your entire Search Console dataset into a local SQLite database, then gives your LLM a pre-built SQL query library for every standard SEO analysis type, with context available for your LLM to perform any SQL query to answer your questions and analyse for you.

Enables async-first working practices by providing tools to draft decision docs, convert meetings to async artifacts, score status updates, and triage sync vs async tasks. It also offers reference tools for the Open and Async book's principles and coaching prompts.

This MCP server provides tools to query Google Search Console data, including search analytics, URL inspection, sitemap management, and site listing. It enables AI assistants to retrieve SEO performance metrics and manage sitemaps through natural language.

Enables reading and controlling a Universal Audio Apollo interface: channel names, faders, preamp gain, cue sends, monitor control, and more via the UA Mixer Engine's local TCP API.

Enables web search via a real browser for any LLM, bypassing anti-bot measures without API keys.

Agent-native browser control MCP server that enables AI agents to browse and interact with web pages via accessibility tree snapshots and ref ID-based commands.

An MCP server that enables AI agents to manage Google Search Console properties, including checking index status, requesting indexing, submitting sitemaps, and pulling search analytics with per-property quota tracking.

Enables building and evaluating LangGraph agents over a protocol-level MCP server to measure failure rates across four agent topologies.