AgentIndex icon
AgentIndex
browser-tools-mcp logo
browser-tools-mcp
★ 7.3k
vs
chrome-devtools-mcp logo
chrome-devtools-mcp
★ 54.0k

browser-tools-mcp vs chrome-devtools-mcp

browser-tools-mcp: BrowserTools MCP empowers AI applications to monitor and interact with browsers through a Chrome extension and Anthropic's Model Context Protocol. It offers a suite of tools for web development audits, including accessibility, performance, and SEO analysis, enhancing AI's capability to understand and improve web pages.; chrome-devtools-mcp: chrome-devtools-mcp enables AI coding assistants like Gemini, Claude, and Copilot to interact with a live Chrome browser via the Model-Context-Protocol (MCP). It grants AI full access to Chrome DevTools for reliable automation, deep debugging, and detailed performance insights.

Editorial Head-to-Head Analysis

Chrome DevTools MCP now covers similar ground (performance traces, network and console inspection, screenshots) from the Chrome team, with fewer moving parts. Browser Tools MCP's distinguishing points are its Lighthouse audit tools and its use of your already-open browser through an extension.

01

TL;DR

browser-tools-mcp logo
browser-tools-mcpBrowser Automation · ★ 7.3k
When to choose:
  • You use Cursor or a similar IDE agent and want it to read console logs, network activity, screenshots and the currently selected DOM element from your own Chrome.
  • You want Lighthouse-based audits for accessibility, performance, SEO and best practices from within the agent.
  • You want browser logs kept local: the README says logs are stored on your machine and never sent to a third-party service.
When to skip:
  • You want the agent to click through and drive pages; this tool is aimed at monitoring and auditing, not full automation.
  • You do not want to install a Chrome extension and run a separate local Node server alongside the MCP server.
  • You want the most actively developed option: the latest release in the data we checked was v2.0.2 on 2026-08-12.
Read browser-tools-mcp full review →
chrome-devtools-mcp logo
chrome-devtools-mcpBrowser Automation · ★ 54.0k
When to choose:
  • You want an agent to record a Chrome performance trace and get insights from it; the README lists performance_start_trace, performance_stop_trace and performance_analyze_insight.
  • You need to inspect network requests, console messages and screenshots of a page while debugging it.
  • You want the agent to attach to a Chrome you already have running, using --browser-url, --ws-endpoint or --autoConnect (Chrome 144+).
When to skip:
  • You need Firefox or Safari: the project is built on Chrome DevTools and targets Chrome.
  • You want a general-purpose automation or test runner across browsers; Playwright MCP is the closer fit.
  • You cannot run Node.js 20.19 or newer, which the README lists as a requirement.
Read chrome-devtools-mcp full review →
02

Side-by-Side Comparison

Field
browser-tools-mcp logobrowser-tools-mcp
chrome-devtools-mcp logochrome-devtools-mcp
Category
Browser Automation
Browser Automation
Stars
★ 7.3k
★ 54.0k
License
MIT
Apache-2.0
Install Command
npx @agentdeskai/browser-tools-mcp@latest
npx -y chrome-devtools-mcp@latest
Updated
1w ago
1d ago
Open Source
Yes
Yes
Website
↗ Visit
↗ Visit
GitHub
↗ GitHub
↗ GitHub
Tags
Browser Automation, AI Tools, Model Context Protocol
Chrome DevTools, AI Assistant, Browser Automation
03

Features

browser-tools-mcp logobrowser-tools-mcp
01Capture browser data (logs, network, DOM, screenshots)
02Integrate with AI via Model Context Protocol (MCP)
03Perform comprehensive web development audits (SEO, Accessibility, Performance)
04Automate headless Chrome for audit data collection
05Provide structured JSON results for AI interpretation
chrome-devtools-mcp logochrome-devtools-mcp
01Get performance insights using Chrome DevTools
02Advanced browser debugging (network, screenshots, console)
03Reliable automation using Puppeteer
04Input automation (click, drag, fill, etc.)
05Navigation automation (new page, navigate, wait for, etc.)
04

Use Cases

browser-tools-mcp logobrowser-tools-mcp
↳Enable AI coding agents to audit and debug web pages
↳Improve web application SEO, performance, and accessibility
↳Automated analysis and enhancement of NextJS applications
chrome-devtools-mcp logochrome-devtools-mcp
↳Automating browser interactions for testing or data extraction
↳Debugging web applications by analyzing network requests and console messages
↳Analyzing website performance by recording traces and extracting insights
05

Best For

browser-tools-mcp logobrowser-tools-mcp
Trending
chrome-devtools-mcp logochrome-devtools-mcp
Most PopularEssentialTrending
FAQ

FAQ

What is the difference between browser-tools-mcp and chrome-devtools-mcp?
Chrome DevTools MCP now covers similar ground (performance traces, network and console inspection, screenshots) from the Chrome team, with fewer moving parts. Browser Tools MCP's distinguishing points are its Lighthouse audit tools and its use of your already-open browser through an extension.
Which is better, browser-tools-mcp or chrome-devtools-mcp?
The best choice depends on your use case. Choose browser-tools-mcp if Enable AI coding agents to audit and debug web pages, and chrome-devtools-mcp if Automating browser interactions for testing or data extraction.
Is browser-tools-mcp free or open source?
Yes, browser-tools-mcp is open source on GitHub (MIT).
Is chrome-devtools-mcp free or open source?
Yes, chrome-devtools-mcp is open source on GitHub (Apache-2.0).
Cloud Infrastructure
Ad

Deploy on DigitalOcean

Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.

Claim $200 Free Credit
→

Related

Alternatives to browser-tools-mcp →Alternatives to chrome-devtools-mcp →browser-tools-mcp details →chrome-devtools-mcp details →chrome-devtools-mcp vs playwright-mcp →Windows-MCP vs chrome-devtools-mcp →