Esta página se muestra en inglés. Una traducción al español está en curso.
MCP ConfigsMay 14, 2026·2 min de lectura

BrowserToolsMCP — Audit Browser Logs via MCP

BrowserToolsMCP streams browser logs to MCP clients: install via `npx`, run a local server, and audit network/console events from your IDE (7.2k★).

MCP Hub
MCP Hub · Community
Listo para agents

Staging seguro para este activo

Este activo primero queda en staging. El prompt copiado pide inspeccionar los archivos staged antes de activar scripts, config MCP o config global.

Stage only · 17/100Política: staging
Superficie agent
Cualquier agent MCP/CLI
Tipo
Mcp Config
Instalación
Stage only
Confianza
Confianza: Established
Entrada
Asset
Comando de staging seguro
npx -y tokrepo@latest install 80bc9d31-f1e5-5528-8e4b-bc93fe9b1d88 --target codex

Primero deja archivos en staging; la activación requiere revisar el README y el plan staged.

Introducción

BrowserToolsMCP streams browser logs to MCP clients: install via npx, run a local server, and audit network/console events from your IDE (7.2k★).

Best for: Debugging agent-driven browser automation (Playwright, extension flows) when you need visibility into console/network signals

Works with: MCP-compatible IDE clients, Chrome/Chromium, and a separate terminal for browser-tools-server as described in the README

Setup time: 8-20 minutes

Main

  • Two-part architecture: the README separates the IDE-side MCP server from the standalone browser-tools-server, which keeps logs flowing even when your IDE restarts.
  • Audit-first workflow: explicitly designed for auditing (network + console) so you can debug “why did the agent do that” issues.
  • IDE friendly: you install the MCP side inside your IDE and keep the server in a separate terminal—simple operational model.
  • Release-tracked extension: provides a versioned Chrome extension zip in GitHub releases, making installs reproducible.

FAQ

  • Do I need the extension?: Yes. The quickstart requires installing the Chrome extension so the server can receive logs.
  • Why run a separate server?: It keeps the log pipeline stable and avoids coupling log collection to your IDE process.
  • How do I start safely?: Install first, then run audits on a simple page to confirm you see console + network events.
🙏

Fuente y agradecimientos

Source: https://github.com/AgentDeskAI/browser-tools-mcp > License: MIT > GitHub stars: 7212 · forks: 521

Discusión

Inicia sesión para unirte a la discusión.
Aún no hay comentarios. Sé el primero en compartir tus ideas.

Activos relacionados

Playwright MCP — Browser Automation Server

Playwright MCP is an MCP server for browser automation via Playwright snapshots. Add via npx in Claude Code/Codex to run deterministic actions.

MCP Configs
MCP Hub

SigNoz MCP Server — Query Traces, Logs & Alerts

SigNoz MCP Server connects MCP clients to your SigNoz instance: query traces/logs, inspect alerts, and automate observability workflows using an API key.

MCP Configs
MCP Hub

sp500-mcp-server — Query S&P 500 Company Data via MCP

sp500-mcp-server is an MCP server + Next.js app for querying S&P 500 company fundamentals, officers, filings, and news via Supabase.

MCP Configs
MCP Hub

MCP SSH Manager — Remote Ops via Claude/Codex

MCP SSH Manager is an MCP server that lets Claude Code and OpenAI Codex manage SSH sessions: run commands, sync files, and automate DevOps routines.

MCP Configs
MCP Hub
◈Inicio🔍Buscar👤Yo