"How to use the browser console" matching MCP servers:

Captures browser console messages (log, warn, error, etc.) and makes them available to AI language models like Claude Code and Gemini CLI for seamless debugging and development.

Enables AI assistants to connect to browser DevTools and backend debuggers for full-stack debugging, including frontend console, network, performance, and backend log analysis.

Bridges browser content, developer tools data, and web page interactions with Claude through MCP. Enables page inspection, DOM analysis, JavaScript execution, console monitoring, network activity tracking, and screenshot capture across multiple browser tabs.

MCP server for browser debugging, inspection, and verification that streams console logs, network errors, and user actions into AI coding assistants.

A Model Context Protocol server that enables LLMs to interact with VS Code's Simple Browser, allowing for browser control, JavaScript execution, console monitoring, and navigation through natural language.

Captures and queries browser console logs from all tabs, enabling AI assistants to debug web applications with search, filtering, and custom debugging playbooks.

An MCP server that captures browser console logs and network requests via the Chrome DevTools Protocol. It allows users to monitor real-time logs, inspect network traffic, and execute JavaScript code directly in the browser context.

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.

Debug bridge inside your web app: an agent reads the DOM, console and network. Any browser.

MCP server for managing i18n translation files — gives your AI agent full control over your app's translations without dumping entire locale files into context.

MCP bridge between Chromium browsers (Arc, Vivaldi, Brave) and Claude Code. 18 browser automation tools (navigate, click, forms, screenshots, GIF recording, console, network) plus a popup chat panel powered by the Claude Agent SDK.

Zero-dependency macOS desktop automation for AI agents. Screenshot, mouse, keyboard, clipboard, and window control via MCP. 18 tools, macOS 13+, one command: npx mac-use-mcp.

Provides native macOS computer control tools including mouse and keyboard simulation, screenshot capture, and application management for MCP-compatible agents. It enables AI assistants to directly interact with the macOS operating system and installed apps through standard tool calls.

Drives a browser - or a native Expo/React Native app - and your dev server, putting both on one correlated timeline so a console error and the backend stack trace from the same moment line up. For Claude Code and AI agents.

A simple MCP server that provides a basic greeting tool and serves as a starter template for AWS Lambda deployment. Demonstrates how to build and deploy MCP servers with both local development and cloud deployment capabilities.

Converts a Figma file into a React project using Ant Design, AG Grid, ApexCharts, and Tailwind CSS, with optional export of mobile screens as a React Native (Expo) app.

MCP server that lets AI editors execute JavaScript, read console output, and simulate clicks/input on static web pages. Supports multiple browser pages and can be deployed remotely via HTTP transport.

An MCP server that edits files through a real Neovim instance, giving agents access to LSP diagnostics, formatting, code actions, and plugin commands.

Gives AI coding tools access to the CSS cascade the way DevTools does — which rules matched, which won, where each came from.

Enables MCP clients to read console logs and network requests from a connected mobile H5 page and, with explicit user authorization, execute JavaScript in that page.