chrome-devtools-mcp
★ 58.7k
vs
terminal-browser
★ 4.7k
chrome-devtools-mcp vs terminal-browser
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.; terminal-browser: terminal-browser renders a real Chromium browser inside a graphics-capable terminal. It supports split-pane previews, SSH workflows and an agent-browser-compatible action CLI for interacting with open browsers.
01
TL;DR
chrome-devtools-mcpBrowser Automation · ★ 58.7k
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.
terminal-browserBrowser Automation · ★ 4.7k
Preview a website beside a coding agent.
02
Side-by-Side Comparison
Field
Category
Browser Automation
Browser Automation
Stars
★ 58.7k
★ 4.7k
License
Apache-2.0
MIT
Install Command
npx -y chrome-devtools-mcp@latest
brew install terminal-browser
Updated
1d ago
1d ago
Open Source
Yes
Yes
Tags
Chrome DevTools, AI Assistant, Browser Automation
browser, claude-code, claude-code-plugin
03
Features
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.)
01Renders browser pixels through the kitty graphics protocol.
02Provides tabs, split panes and developer tools.
03Action commands let agents interact with open browsers.
04
Use Cases
↳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
↳Preview a website beside a coding agent.
↳Inspect a remote development site over SSH.
↳Operate a browser through compatible agent commands.
05
Best For
Most PopularEssentialTrending
—
FAQ
FAQ
What is the difference between chrome-devtools-mcp and terminal-browser?
Both chrome-devtools-mcp and terminal-browser are in the Browser Automation category. chrome-devtools-mcp has 58.7k stars, while terminal-browser has 4.7k stars.
Which is better, chrome-devtools-mcp or terminal-browser?
The best choice depends on your use case. Choose chrome-devtools-mcp if Automating browser interactions for testing or data extraction, and terminal-browser if Preview a website beside a coding agent..
Is chrome-devtools-mcp free or open source?
Yes, chrome-devtools-mcp is open source on GitHub (Apache-2.0).
Is terminal-browser free or open source?
Yes, terminal-browser is open source on GitHub (MIT).
Cloud Infrastructure
AdDeploy on DigitalOcean
Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.
→