Browser MCP Agent vs Chrome DevTools MCP
Side-by-side comparison built from DeepYard's structured catalog. Content updated Aug 21, 2026.
Direct Answer
Browser MCP Agent suits teams needing open-source access, browser navigation focus, and 133,530 GitHub stars in current listing data. Chrome DevTools MCP suits teams needing open-source access, browser automation focus, and 49,556 GitHub stars in current listing data. This summary reflects catalog metadata only for decision support, not independent testing.
What this comparison weighs
- Pricing and free-tier availability
- License model and deployment fit
- GitHub adoption and contributor depth
- Catalog tags, integrations, and supported workflows
| Metric | Browser MCP Agent | Chrome DevTools MCP |
|---|---|---|
| GitHub Stars | 133.5K | 49.6K |
| Contributors | 95 | 118 |
| Last Commit | Aug 22, 2026 | Aug 21, 2026 |
| Open Issues | 14 | 90 |
| License | open-source | open-source |
| Pricing | open-source | open-source |
| Free Tier | Yes | Yes |
| Category | mcp-servers | mcp-servers |
| Trending | No | No |
Choose Browser MCP Agent if you need
- • Browser MCP Agent is the stronger pick when Browser Navigation matters because that capability is listed only on its profile.
- • Browser MCP Agent shows broader GitHub adoption with 133,530 stars versus 49,556 for Chrome DevTools MCP.
- • Browser MCP Agent is the cleaner fit if you specifically need Mcp workflows from the catalog tags.
Choose Chrome DevTools MCP if you need
- • Chrome DevTools MCP is the stronger pick when Browser Automation matters because that capability is listed only on its profile.
- • Chrome DevTools MCP has a larger visible contributor base (118 vs 95).
- • Chrome DevTools MCP is the cleaner fit if you specifically need Chrome workflows from the catalog tags.
Meaningful differences
- • GitHub adoption: Browser MCP Agent shows 133,530 stars versus 49,556 for Chrome DevTools MCP.
- • Contributor count: Browser MCP Agent lists 95 contributors and Chrome DevTools MCP lists 118.
Shared capabilities
- • No shared capabilities are explicitly listed in the stored metadata.
Shared Tags
Only in Browser MCP Agent
Only in Chrome DevTools MCP
Limitations and evidence
- • DeepYard compares structured public metadata; this is not an independent benchmark unless a test record is shown.
- • Signals such as stars, contributors, and last commit indicate public activity, not purchase fit or runtime quality.
- • Pricing and feature coverage reflect the stored listing snapshot and may lag vendor changes between refreshes.
Source links
About Browser MCP Agent
A Model Context Protocol agent that provides browser automation capabilities to AI assistants. It can navigate to URLs, click elements, fill forms, take screenshots, and extract structured data from web pages. Built as an MCP server, it integrates with Claude Code, Cursor, and other MCP-compatible clients to give AI models real-time web interaction abilities. Part of the awesome-llm-apps collection.
View full listingAbout Chrome DevTools MCP
An official Google MCP server that gives AI coding agents full access to Chrome DevTools. Enables performance trace recording with actionable insights, advanced debugging (network requests, screenshots, console messages with source-mapped stack traces), and reliable Puppeteer-based browser automation with automatic result waiting. Supports headless mode for servers, isolated mode with temp user data, and WebSocket connection to existing Chrome instances.
View full listing