chrome-devtools-mcp vs browser-rs-mcp
Chrome browser access for AI agents, compared
chrome-devtools-mcp and browser-rs-mcp let MCP-compatible agents automate and inspect a live Chrome browser. chrome-devtools-mcp emphasizes DevTools-based debugging and performance analysis, while browser-rs-mcp focuses on sharing one persistent browser profile across agents in separate tabs.
chrome-devtools-mcp: Give Coding Agents Chrome DevTools Access
Chrome DevTools MCP lets coding agents inspect and control a live Chrome browser for automation, debugging, and performance analysis. It is an actively maintained TypeScript MCP server for teams that want browser workflows grounded in DevTools.
browser-rs-mcp: Share Chrome with AI Agents
A Rust MCP server that lets multiple AI agents control separate tabs in one shared Chrome profile. It provides browser automation through Chrome DevTools Protocol without requiring a Node.js runtime.
| chrome-devtools-mcp | browser-rs-mcp | |
|---|---|---|
| Language | TypeScript | Rust |
| License | Apache-2.0 | Apache-2.0 |
| Stars | 53.1k | 25 |
| Forks | 5.8k | 3 |
| Last analyzed | Oct 9, 2026 | Oct 4, 2026 |
Key differences
- chrome-devtools-mcp includes performance trace recording and analysis; browser-rs-mcp highlights shared browsing and parallel agent workflows.
- chrome-devtools-mcp is written in TypeScript and requires Node.js; browser-rs-mcp is written in Rust and does not require a Node.js runtime.
- chrome-devtools-mcp also offers a CLI, while browser-rs-mcp supports stdio and HTTP transports for MCP clients.
- browser-rs-mcp lets multiple agents share a Chrome process and persistent profile using owner-scoped tabs; chrome-devtools-mcp supports connections to existing Chrome instances and isolated sessions.
- chrome-devtools-mcp reports 52.9k stars and 5.5k forks; browser-rs-mcp reports 25 stars and 3 forks.
Choose chrome-devtools-mcp if you…
- need Chrome DevTools performance traces, console and network inspection, or source-mapped stack traces.
- want a CLI for browser tasks without an MCP client.
- need a TypeScript project that supports headless or isolated sessions and connections to existing Chrome instances.
Choose browser-rs-mcp if you…
- want multiple agents to use one persistent Chrome profile in separate owner-scoped tabs.
- need a Rust MCP server without a Node.js runtime, with stdio or HTTP transports.
- are building workflows around shared logged-in browsing, parallel research, scraping, or QA.
Compare the numbers side by side, or add more projects
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.