chrome-devtools-mcp vs Uni-CLI
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.; Uni-CLI: Uni-CLI is a command-line tool that lets agents search by intent and execute governed commands across websites, apps, local tools, and system capabilities. It returns structured AgentEnvelopes with evidence for agent inspection and repair. The tool supports self-repair, MCP/ACP protocols, and local computer control.
TL;DR
- 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+).
- 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.
Search Hacker News frontpage and fetch top stories
Side-by-Side Comparison
chrome-devtools-mcpUni-CLIFeatures
chrome-devtools-mcpUni-CLIUse Cases
chrome-devtools-mcpUni-CLIBest For
chrome-devtools-mcpUni-CLIFAQ
Deploy on DigitalOcean
Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.