"How to use the browser console log and network tab" matching MCP servers:

This gives Claude Desktop access to browser automation tools for web scraping, form filling, and more.

Launches multiple Browser-Use agents to automatically test websites for UI bugs, broken links, accessibility issues, and other technical problems on both live and localhost sites.

Provides AI clients with deterministic Playwright-driven browser control, enabling navigation, interaction, screenshots, and inspection of rendered HTML, computed styles, console diagnostics, and font audits without an embedded LLM or API key.

Enables AI agents to autonomously operate web browsers through the Model Context Protocol, including navigating pages, clicking, typing, filling forms, and extracting structured data.

Exposes MCP tools that let an agent search a catalog, inspect a paid service's pricing, fetch it with payment handled automatically, and check its remaining budget and active spending limits. Payments are authorized against a signed mandate from the owner, so agents can buy API access over HTTP 402 without ever holding the owner's private key.

Captures browser console logs via Chrome DevTools Protocol and exposes them to MCP clients over SSE, enabling log retrieval with the getConsoleLogs tool.

An MCP server that connects any MCP client (like Claude or Cursor) with the browser using browser-use, allowing clients to utilize existing LLMs without requiring additional API keys.

Enables the Pi coding agent to drive Chrome through DevTools, providing browser automation tools, persistent or isolated profiles, screenshots, page analysis, and bundled agent policies.

Enables an MCP-capable AI chat to control selected tabs in a separate persistent Chromium browser, protected by OAuth, per-tab grants, and local approvals.

Enables any MCP-connected agent to drive a browser by reading each page as an indexed action-space table and performing one guarded operation on a numbered target, refusing and refreshing when the page changes instead of retrying selectors.

Enables browser automation using Python scripts, offering operations like taking webpage screenshots, retrieving HTML content, and executing JavaScript.

AI-driven browser automation server that implements the Model Context Protocol to enable natural language control of web browsers for tasks like navigation, form filling, and visual interaction.

Facilitates browser automation with custom capabilities and agent-based interactions, integrated through the browser-use library.

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 through MCP clients like Claude or Cursor, using the client's existing LLM without requiring an additional API key.

Enables AI agents to control and automate browser actions through an MCP server deployed on Heroku. Supports programmatic browser automation with natural language tasks across multiple LLM providers.

Enables AI agents to interact with web browsers using natural language, featuring automated browsing, form filling, vision-based element detection, and structured JSON responses for systematic browser control.

A FastMCP server that enables browser automation through natural language commands, allowing Language Models to browse the web, fill out forms, click buttons, and perform other web-based tasks via a simple API.

MCP server that adds billing and settlement to any MCP server, enabling paid tool calls with configurable pricing, spending limits, and automatic invoicing through the AllScale CLI.

A minimal MCP server with get_weather and create_ticket tools, used for testing MCP servers across protocol, unit, eval, transport, and auth layers.

An MCP server for automating browser tasks using the Browser Use API. Provides tools to run, monitor, and manage browser automation tasks.

Enables an AI app to call functions exposed as MCP tools by a web page through a relay while the page stays open in a browser tab. Nothing needs to be installed locally.

Enables MCP-driven browser automation from any MCP client by pairing with a Chrome extension, translating tool calls into WebSocket commands to drive Chrome without an Electron host.

Enables AI assistants to browse websites, extract information, fill forms, interact with pages, and execute multi-step web tasks autonomously.

An MCP server that lets AI coding agents save immutable, versioned Markdown reports into md-log, a human-in-the-loop review and archive layer for vibe coding.

Enables coding agents to drive a real Chrome browser to complete natural-language web tasks and return evidence for verification.

An MCP server that enables remote observation and control of a Chromium browser via a WebSocket relay, supporting DOM, CDP, and native OS automation for local or LAN-based AI agents.

A Windows-only MCP server for controlling a real browser using native screenshots, Windows accessibility, and node-interception mouse/keyboard input, without CDP or Playwright.

An AI recipe recommendation server based on the MCP protocol, providing functions such as recipe query, classification filtering, intelligent dietary planning, and daily menu recommendation.

A TypeScript-based MCP server that implements a simple notes system, allowing users to create, access, and generate summaries of text notes through Claude Desktop.

This server provides a note storage system with a custom URI scheme, allowing users to add and summarize notes, with adjustable summary detail levels.

Enables users to turn their current Codex/ChatGPT conversation into a source-backed personal newspaper: they pick public sources, exclusions, language, timezone and interests through native settings, then request an edition that the conversation reads and cites. The server stores and renders validated editions locally with source links, preserving the previous edition when generation fails.

MCP server that gives AI agents secure, consent-based access to a single browser tab, supporting read-only snapshots, element interaction with per-action approval, and frozen multi-step plans, all audited.

An MCP server that enables AI assistants to control a web browser through natural language commands, allowing them to navigate websites and extract information via SSE transport.

Enables AI agents to read the titles and URLs of open browser tabs in Chrome and Edge, and to create, update, and ungroup tab groups through a local, token-authenticated connection. It also exposes the tabs of a group so their links can be copied as a URL list or Markdown.

Enables MCP-capable agent CLIs on macOS to reuse an installed, unmodified OpenAI Browser Runtime to drive a connected Chrome or Edge browser (or a host's in-app browser backend) through js, js_reset, and turn_ended tools. It stays a thin bridge that preserves the Runtime's approval and security boundaries, failing closed when the client cannot handle approval requests.

Enables local AI agents to control Chrome in parallel with isolated tab groups, supporting operations like navigation, clicks, and form filling without interference.

MCP server enabling LLMs to perform browser tasks via SSE transport, allowing clients like Cursor.ai and Claude to open websites and interact with web content through natural language commands.

Multi-agent swarm orchestrator for AI workflows. Exposes blackboard read/write, agent dispatch, permission gating (AuthGuardian), token budget enforcement (FederatedBudget), and audit log tools over MCP. Supports 14 AI framework adapters including LangChain, AutoGen, CrewAI, Codex, and A2A — mix any frameworks in one swarm with race-condition-safe shared state.(Traffic light for agents)

The logs of everything on one machine — app, build, GPU, containers, serial board, OS — interleaved in the order they happened, and readable by an agent. Read-only: it can tail, search and wait, and it cannot write, delete or configure anything.