Chrome DevTools MCP vs GitHub MCP
Side-by-side comparison built from DeepYard's structured catalog. Content updated Aug 21, 2026.
Direct Answer
Chrome DevTools MCP suits teams needing open-source access, browser automation focus, and 49,556 GitHub stars in current listing data. GitHub MCP suits teams needing open-source access, repo management focus, and 32,422 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 | Chrome DevTools MCP | GitHub MCP |
|---|---|---|
| GitHub Stars | 49.6K | 32.4K |
| Contributors | 118 | 155 |
| Last Commit | Aug 21, 2026 | Aug 21, 2026 |
| Open Issues | 90 | 327 |
| License | open-source | open-source |
| Pricing | open-source | open-source |
| Free Tier | Yes | Yes |
| Category | mcp-servers | mcp-servers |
| Trending | No | No |
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 shows broader GitHub adoption with 49,556 stars versus 32,422 for GitHub MCP.
- • Chrome DevTools MCP is the cleaner fit if you specifically need Chrome workflows from the catalog tags.
Choose GitHub MCP if you need
- • GitHub MCP is the stronger pick when Repo Management matters because that capability is listed only on its profile.
- • GitHub MCP has a larger visible contributor base (155 vs 118).
- • GitHub MCP is the cleaner fit if you specifically need Github workflows from the catalog tags.
Meaningful differences
- • GitHub adoption: Chrome DevTools MCP shows 49,556 stars versus 32,422 for GitHub MCP.
- • Contributor count: Chrome DevTools MCP lists 118 contributors and GitHub MCP lists 155.
Shared capabilities
- • No shared capabilities are explicitly listed in the stored metadata.
Shared Tags
Only in Chrome DevTools MCP
Only in GitHub 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 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 listingAbout GitHub MCP
GitHub's official MCP server brings the entire GitHub API surface into your AI coding workflow. Create and review pull requests, manage issues, search code across repositories, read file contents, list branches, and trigger Actions runs — all without leaving your editor. Authenticate once with a GitHub Personal Access Token and let Claude Code interact with any repository you have access to.
View full listing