codegraph vs context7
Two of the top mcp servers for developers, side by side: score, setup, license, activity and what each review found.
codegraph
Local code knowledge graph served to coding agents over MCP
context7
Fetches current, version-specific library docs into coding agent prompts
| What we compare | codegraph | context7 |
|---|---|---|
| Score parts, out of 100 | ||
| Adoption | 92, widely used | 80, popular |
| Freshness | 100, active | 100, active |
| Maintenance | 91, healthy | 99, healthy |
| Easy to run | 50, easy | 0, hard |
| Agent-ready | 85, ready | 0, none |
| Facts from GitHub and the README | ||
| Stars | 73.7k | 62.9k |
| License | MIT (permissive) | MIT (permissive) |
| Last commit | Oct 2026 | Oct 2026 |
| Last release | Oct 2026 | Oct 2026 |
| Language | C | TypeScript |
| Docker | No | No |
| GPU | Not needed | Not needed |
| arm64 or Apple Silicon | Mentioned | Not stated |
codegraph
CodeGraph indexes a project into a local graph of symbols, call edges and dependencies under `.codegraph/`, then exposes it to coding agents through an MCP server. Agents can fetch relevant source, call paths and change impact in one call instead of grepping and reading files. `codegraph install` wires it into Claude Code, Cursor, Codex CLI, opencode, Gemini CLI, Kiro, GitHub Copilot and others, and auto-sync keeps the index current.
Who it is for: Developers using AI coding agents on mid-to-large codebases
Strengths
- Runs locally; no Node.js needed, ships as a bundled installer or npm package
- One `codegraph install` configures MCP for nine named agents and IDEs
- Covers 30+ languages, including TypeScript, Python, Go, Rust, Java, C#, Swift
- Watches files and updates the graph automatically; no manual re-index
Weaknesses
- README admits about 80% more retrieval context stays resident in long sessions
- Published benchmarks are the author's, on 7 repos with one question each
- No Docker or compose setup; install is via curl/PowerShell script or npm
- Hosted CodeGraph platform is a waitlist product, separate from this repo
- no GPU
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