chrome-devtools-mcp vs context7
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
context7
Fetches current, version-specific library docs into coding agent prompts
| What we compare | chrome-devtools-mcp | context7 |
|---|---|---|
| Score parts, out of 100 | ||
| Adoption | 69, popular | 80, popular |
| Freshness | 100, active | 100, active |
| Maintenance | 79, fair | 99, healthy |
| Easy to run | 33, some setup | 0, hard |
| Agent-ready | 30, minimal | 0, none |
| Facts from GitHub and the README | ||
| Stars | 53.3k | 62.9k |
| License | Apache-2.0 (permissive) | MIT (permissive) |
| Last commit | Oct 2026 | Oct 2026 |
| Last release | Sep 2026 | Oct 2026 |
| Language | TypeScript | TypeScript |
| Docker | No | No |
| GPU | Not needed | Not needed |
| arm64 or Apple Silicon | Not stated | Not stated |
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)
context7
Context7 looks up documentation and code examples for a named library and version, then returns them to the coding agent as context. It runs as an MCP server with two tools (resolve-library-id, query-docs) or as a ctx7 CLI plus skill. Setup is one command, npx ctx7 setup, which handles OAuth and API key generation. The hosted service at mcp.context7.com does the retrieval.
Who it is for: Developers using AI coding agents who need current library docs
Strengths
- Two modes: MCP server, or ctx7 CLI with an installed skill
- Library IDs like /vercel/next.js skip matching; version can be named in the prompt
- npx ctx7 setup configures Cursor, Claude Code or opencode
- Also ships a TypeScript SDK and Vercel AI SDK tools
Weaknesses
- API backend, parsing and crawling engines are private; repo has only the MCP server
- Relies on the hosted service at mcp.context7.com; local run is a separate guide
- Free API key recommended for higher rate limits; exact limits unknown
- Docs are community-contributed; accuracy and security are not guaranteed
- no GPU
- Needs Node.js 18+, Context7 hosted API