# 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★).

## Install

Merge the JSON below into your `.mcp.json`:

## Quick Use

```bash
npx @agentdeskai/browser-tools-mcp@latest
npx @agentdeskai/browser-tools-server@latest
# Install the Chrome extension from the release zip (see README)
```

## Intro

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 & Thanks

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

---

<!-- ZH -->

## Quick Use

```bash
npx @agentdeskai/browser-tools-mcp@latest
npx @agentdeskai/browser-tools-server@latest
# 从 release zip 安装 Chrome 扩展（见 README）
```

## Intro

BrowserToolsMCP 把浏览器日志接到 MCP 客户端：用 `npx` 安装，另起 `browser-tools-server`，在 IDE 中审计 network/console 事件（7212★）。

**Best for:** 做 agent 驱动的浏览器自动化（Playwright/扩展流程）时，需要把 console/network 信号变得可观测、可追溯

**Works with:** 支持 MCP 的 IDE 客户端、Chrome/Chromium，以及按 README 另开终端运行 `browser-tools-server`

**Setup time:** 8-20 minutes

## Main

- **两段式架构**：README 把 IDE 侧 MCP server 与独立的 `browser-tools-server` 分开，IDE 重启也不影响日志流转。
- **审计优先**：面向 network/console 审计，专治“agent 为什么这么点/这么跳转”的不可解释问题。
- **IDE 友好**：IDE 里装 MCP 配置，另开终端跑 server，运维模型简单清晰。
- **可复现的扩展安装**：GitHub Releases 提供版本化 extension zip，便于团队统一版本。

### FAQ

- **必须装扩展吗？**: 必须。Quickstart 需要安装 Chrome extension 才能把日志送到 server。
- **为什么要另起一个 server？**: 让日志采集与 IDE 解耦，链路更稳定、也更容易排错。
- **怎么安全起步？**: 先按 README 装好，再用一个简单页面做 audit，确认能看到 console/network 事件。

## Source & Thanks

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


---
Source: https://tokrepo.com/en/workflows/browsertoolsmcp-audit-browser-logs-via-mcp
Author: MCP Hub