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

Turns application errors into reviewed pull requests by automating root-cause analysis, Jira ticket creation, local and CI test gates, and GitHub PRs, with a human as the final merge gate.

A production-ready Model Context Protocol server implementation that connects AI assistants to the TON blockchain, allowing them to query wallet balances, transaction details, smart contracts, and other blockchain 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.

Browser use using Typesafe's Jev model

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

Self-hosted MCP server for AI browser automation. Connects to your own Chromium instance via CDP, providing tools for browser control, navigation, interaction, and content extraction.

Gives an AI assistant a persistent, stealth-configured Chrome browser that stays logged in across sessions, supports interactive first login, and can autofill credentials from the macOS Keychain and replay WebAuthn passkeys for sites that block scripted login.

Enables AI assistants to control a web browser through Playwright-compatible tools, with an on-device decision engine for autonomous task completion and optional LLM escalation.

MCP server for AI browser automation with tools for navigation, actions, data extraction, and scripting, supporting local and cloud execution.

Enables AI agents to navigate the web visually using screenshot-based interaction and Set-of-Mark labeling for interactive elements. It supports humanized browsing behaviors, anti-detection measures, and complex tasks like multi-click CAPTCHA solving.

An MCP server that enables AI agents to control a real Chrome browser with full login state through 37 structured automation tools, connecting via the Playwriter extension without needing a remote debugging port.

A Model Context Protocol server that converts Markdown content to HTML format.

Enables AI agents to control your installed Google Chrome through MCP or HTTP using compact text snapshots, exact pixel coordinates, and a visible cursor. It provides browser tools for navigation, clicking, typing, scrolling, tabs, forms, waiting, recording, and human handoff.

An AI-centric MCP server that enables automated Xilinx Vivado workflows, including project management, synthesis, implementation, and timing analysis. It allows AI agents to drive hardware design processes while integrating directly with the official Vivado GUI for visual context.

Gives AI agents a single shared, logged-in Chrome they can drive over MCP or plain HTTP: open and read tabs, click, type, upload files, run short Playwright scripts, hand off whole web tasks to a cheaper model, and keep per-site memory. Agents work in background windows they own without stealing the user's mouse or closing their tabs.

Enables AI agents to control a persistent Chrome browser through a local daemon, with Jev performing routine actions and the host agent handling reasoning, text, and verification.

Enables browser automation in which a planning LLM states one outcome at a time while a Typesafe System One model decides which element, action, and value to use, with Playwright carrying it out. Exposes tools for opening pages, driving multi-step goals, checking or choosing among options, reading relevant page text, acting on elements directly, and calling a page's own WebMCP tools.

Enables browser automation where a calling LLM states one desired outcome per step and a separate decision model chooses the element, action, value, and completion status, with Playwright carrying out the action. Exposes tools for navigating, performing and verifying steps, reading question-relevant page text, taking snapshots, capturing screenshots, and invoking tools that pages register for agents.

Enables browser automation through MCP clients like Claude or Cursor, using the client's existing LLM without requiring an additional API key.

Enables MCP clients to automate a real browser by stating one outcome at a time in natural language, with a decision model (Jev) choosing each element, action, and value while code drives Playwright. Also exposes tools to open pages, verify questions, read page content, snapshot elements, act directly, and call a page's WebMCP tools.