# Chrome MCP Server — Extension-Based Browser MCP

> mcp-chrome turns Chrome into an MCP server via an extension + bridge. Install mcp-chrome-bridge, load the extension, then connect to 127.0.0.1:12306/mcp.

## Install

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

## Quick Use

1. Install the verified entrypoint:

```bash
npm install -g mcp-chrome-bridge
```

2. Run a first local check:

```bash
Load the extension via chrome://extensions/ (Developer mode → Load unpacked)
```

3. Add a repeatable verification step:

```bash
Configure MCP client URL: http://127.0.0.1:12306/mcp
```

---

## Intro

Chrome MCP Server is a verified GitHub-backed asset sourced from `hangwin/mcp-chrome` with 11,586 stars and a MIT license snapshot. Best for: users who want Chrome automation via MCP without spawning a separate browser process, relying on an installed extension. Works with: Node.js 20+, Chrome/Chromium, MCP clients that support streamable HTTP or stdio (per repo). Setup time: 10 minutes.

### Quantitative notes

- Default MCP URL http://127.0.0.1:12306/mcp (repo)
- Node.js >= 20 requirement (repo)

---

## Deep Dive

### What it solves

Use this when you need a **repeatable, team-shareable workflow** instead of one-off agent prompts. The goal is to make installation, first-run validation, and rollback **predictable**.

### Minimal mental model

- Treat the GitHub repo as the source of truth: install instructions, configs, and upgrade paths live there.
- Keep your first run small: one command, one verification, one rollback plan.
- Capture a baseline: setup time, first successful run, and one real task completed end-to-end.

### Safe rollout checklist

1. **Verify source**: confirm repo URL, stars, and license match what you expect.
2. **Install** using the Quick Use commands above.
3. **Prove it works** with the verification command; save the output in a note or issue.
4. **Operationalize**: document owner, upgrade command, and rollback command.

### Troubleshooting (common)

- **Install succeeds but nothing shows up**
  - Likely cause: the tool needs a restart/reload (CLI/IDE) or a config file in the right path.
  - Fix: restart the client, then re-run the verification step.

- **Works on one machine, fails on another**
  - Likely cause: Node/Python/Docker versions differ or missing system dependencies.
  - Fix: pin versions (Node/Python), and copy a minimal known-good config.

- **Token cost or latency is worse than expected**
  - Likely cause: tool schemas or verbose outputs get injected into context.
  - Fix: prefer smaller steps, cache results, and keep tool responses concise when possible.


---

### FAQ

**Q: Why does pnpm need extra steps?**
A: The README notes pnpm may disable postinstall scripts; use the enable-pre-post-scripts setting or run manual registration.

**Q: Is this safe for multi-agent use?**
A: Prefer one controlling client at a time and treat browser state as shared; create clear ownership in your workflow.

**Q: How do I verify it's connected?**
A: Use the extension UI to connect, then ensure your MCP client can enumerate the server and call a simple tool.

---

## Source & Thanks

> GitHub: https://github.com/hangwin/mcp-chrome
> Owner avatar: https://avatars.githubusercontent.com/u/12791725?v=4
> License (SPDX): MIT
> Stars (verified via `api.github.com/repos/hangwin/mcp-chrome`): 11,586


---

<!-- ZH -->

# Chrome MCP——用扩展把 Chrome 变成 MCP Server

> mcp-chrome 通过“浏览器扩展 + bridge”把 Chrome 变成 MCP Server：安装 mcp-chrome-bridge，加载扩展并连接后，客户端可通过 http://127.0.0.1:12306/mcp 访问浏览器能力。

## 快速使用

1. 安装（以仓库为准）：

```bash
npm install -g mcp-chrome-bridge
```

2. 首次运行/检查：

```bash
Load the extension via chrome://extensions/ (Developer mode → Load unpacked)
```

3. 可重复验证：

```bash
Configure MCP client URL: http://127.0.0.1:12306/mcp
```

---

## 简介

Chrome MCP 已核验来源于 `hangwin/mcp-chrome`（11,586 stars，许可证 MIT）。适合：希望用 MCP 驱动 Chrome，但不想每次都启动独立浏览器进程、可接受安装扩展的用户。兼容：Node.js 20+、Chrome/Chromium；支持 streamable HTTP 或 stdio 的 MCP client（仓库）。装机时间：10 分钟。

### 量化信息

- 默认 MCP URL： http://127.0.0.1:12306/mcp（仓库）
- 需要 Node.js >= 20（仓库）

---

## 深度说明

### 解决什么问题

把“找到项目 → 安装 → 首次验证 → 回滚/升级”变成可复用流程，避免只靠一次性提示词或截图操作。

### 最小心智模型

- GitHub 仓库是事实来源：安装、配置、升级、已知问题都以它为准。
- 第一次只做最小闭环：一个命令安装、一个命令验证、一个可回滚方案。
- 记录基线：装机耗时、首次成功输出、完成 1 个真实任务的证据。

### 安全推广清单

1. **核验来源**：确认仓库 URL / stars / license 与预期一致。
2. 按“快速使用”完成安装与首次检查。
3. 跑通“验证命令”，把输出留档。
4. 标注 owner，并写清升级/回滚步骤。

### 常见排障

- **装了但看不到效果**
  - 常见原因：需要重启 CLI/IDE 或配置文件路径不对。
  - 处理：重启后再跑一遍“验证命令”。

- **一台机器能跑，另一台不行**
  - 常见原因：Node/Python/Docker 版本差异或缺少系统依赖。
  - 处理：固定版本，并拷贝最小可用配置。

- **token 成本/延迟超预期**
  - 常见原因：工具 schema 或输出过长被塞进上下文。
  - 处理：拆小步骤、缓存结果、尽量让工具输出更短。


---

### FAQ

**Q: 为什么 pnpm 需要额外步骤？**
A: README 提到 pnpm 默认可能禁用 postinstall；可开启 enable-pre-post-scripts 或手动执行 register。

**Q: 多 agent 同时用安全吗？**
A: 建议同一时间只让一个 client 控制浏览器，把浏览器状态当作共享资源，明确“谁是驾驶员”。

**Q: 怎么确认连通？**
A: 先在扩展 UI 里完成 connect，再让 MCP client 枚举 server 并调用一个最小工具验证。

---

## 来源与感谢

> GitHub：https://github.com/hangwin/mcp-chrome
> Owner avatar：https://avatars.githubusercontent.com/u/12791725?v=4
> 许可证（SPDX）：MIT
> GitHub stars（已通过 `api.github.com/repos/hangwin/mcp-chrome` 核验）：11,586


---
Source: https://tokrepo.com/en/workflows/chrome-mcp-server-extension-based-browser-mcp
Author: MCP Hub