Cette page est affichée en anglais. Une traduction française est en cours.
MCP ConfigsMay 14, 2026·2 min de lecture

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
Prêt pour agents

Cet actif peut être lu et installé directement par les agents

TokRepo expose une commande CLI universelle, un contrat d'installation, le metadata JSON, un plan selon l'adaptateur et le contenu raw pour aider les agents à juger l'adaptation, le risque et les prochaines actions.

Native · 94/100Policy : autoriser
Surface agent
Tout agent MCP/CLI
Type
Mcp
Installation
Bundle
Confiance
Confiance : Established
Point d'entrée
npx @agentdeskai/browser-tools-mcp@latest
Commande CLI universelle
npx tokrepo install 80bc9d31-f1e5-5528-8e4b-bc93fe9b1d88
contrat d'installationJSON metadataplan adaptateurcontenu raw
Introduction

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.
🙏

Source et remerciements

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

Fil de discussion

Connectez-vous pour rejoindre la discussion.
Aucun commentaire pour l'instant. Soyez le premier à partager votre avis.

Actifs similaires

Playwright MCP — Browser Automation for Agents

Playwright MCP exposes browser automation via MCP with device emulation; verified 5,510★ and documents 143 device profiles plus `playwright install` setup.

MCP Configs
MCP Hub

kubernetes-mcp-server — Kubernetes Tools via MCP

kubernetes-mcp-server exposes Kubernetes operations to MCP clients with npx/uvx/binary run modes; verified 1584★ and pushed 2026-05-14.

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

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
◈Accueil🔍Rechercher👤Moi