chrome-devtools-mcp vs github-mcp-server
Two of the top mcp servers for developers, side by side: score, setup, license, activity and what each review found.
chrome-devtools-mcp
MCP server that lets coding agents drive and debug a live Chrome
github-mcp-server
MCP server exposing GitHub repos, issues, PRs and Actions to AI tools
| What we compare | chrome-devtools-mcp | github-mcp-server |
|---|---|---|
| Score parts, out of 100 | ||
| Adoption | 69, popular | 32, known |
| Freshness | 100, active | 100, active |
| Maintenance | 80, healthy | 85, healthy |
| Easy to run | 33, some setup | 50, easy |
| Agent-ready | 30, minimal | 0, none |
| Facts from GitHub and the README | ||
| Stars | 53.3k | 33.5k |
| License | Apache-2.0 (permissive) | MIT (permissive) |
| Last commit | Oct 2026 | Oct 2026 |
| Last release | Sep 2026 | Oct 2026 |
| Language | TypeScript | Go |
| Docker | No | Yes |
| GPU | Not needed | Not needed |
| arm64 or Apple Silicon | Not stated | Mentioned |
chrome-devtools-mcp
chrome-devtools-mcp is an MCP server that gives coding agents such as Claude, Cursor and Copilot control of a live Chrome browser. It records performance traces through Chrome DevTools, inspects network requests and console messages with source-mapped stack traces, and automates page actions via puppeteer. A CLI is included for use without MCP, and a --slim mode exposes a smaller tool set.
Who it is for: Developers who want their coding agent to debug and test pages in Chrome
Strengths
- Records DevTools performance traces and extracts insights from them
- Puppeteer-based automation waits for action results automatically
- Slim mode limits the exposed tools to basic browser tasks
- Also ships a CLI for use without an MCP client
Weaknesses
- Usage statistics are sent to Google by default; opt out with --no-usage-statistics
- Performance tools may send trace URLs to the Google CrUX API
- Officially supports only Chrome and Chrome for Testing
- Exposes all browser content to the connected MCP client
- no GPU
- Needs Node.js LTS, npm, Google Chrome (current stable)
github-mcp-server
Official GitHub MCP server, written in Go, that lets MCP hosts read code, manage issues and pull requests, inspect Actions runs and review security alerts. It runs either as a GitHub-hosted remote endpoint (api.githubcopilot.com/mcp/) or locally over stdio via the ghcr.io Docker image or a binary built with go build. Authentication is OAuth or a personal access token.
Who it is for: Developers wiring AI agents and IDE assistants to GitHub
Strengths
- Hosted remote endpoint needs no local install; local Docker image and Go build also available
- Supports OAuth login or PAT; PAT takes precedence when set
- Works with GitHub Enterprise Cloud (ghe.com) and Enterprise Server via GITHUB_HOST
- Install guides for VS Code, Claude, Cursor, Windsurf, Zed, Codex and others
Weaknesses
- Enterprise Server is not supported by the remote server; local server only
- Remote OAuth needs each host to configure a GitHub App or OAuth App
- Local Docker OAuth needs a fixed callback port (8085) published to loopback
- Only talks to GitHub; no other forges or providers
- no GPU
- Docker
- Needs GitHub API, Docker (optional)