codebase-memory-mcp vs context7

Two of the top mcp servers for developers, side by side: score, setup, license, activity and what each review found.

33rd of 6 in MCP servers for developers

codebase-memory-mcp

MCP server that indexes codebases into a queryable knowledge graph

62 out of 100
#44th of 6 in MCP servers for developers

context7

Fetches current, version-specific library docs into coding agent prompts

57 out of 100
codebase-memory-mcp vs context7: score parts and facts
What we comparecodebase-memory-mcpcontext7
Score parts, out of 100
Adoption47, known80, popular
Freshness100, active100, active
Maintenance81, healthy99, healthy
Easy to run50, easy0, hard
Agent-ready0, none0, none
Facts from GitHub and the README
Stars46.3k62.9k
LicenseMIT (permissive)MIT (permissive)
Last commitOct 2026Oct 2026
Last releaseSep 2026Oct 2026
LanguageCTypeScript
DockerNoNo
GPUNot neededNot needed
arm64 or Apple SiliconMentionedNot stated

codebase-memory-mcp

A native C executable that parses repositories with tree-sitter (162 languages) into a persistent graph of functions, classes, call chains, HTTP routes and cross-service links, and exposes it through 17 MCP tools. It adds semantic search with bundled embeddings, Cypher-like queries, dead code detection, git diff impact mapping and a built-in 3D graph UI. Processing is local, and `install` configures detected coding-agent clients.

Who it is for: Developers giving coding agents structural code search over local repos

Strengths

  • Runs locally with no API key, hosted service or language runtime
  • Bundled embeddings enable semantic search without Ollama or Docker
  • Covers 162 languages; Hybrid LSP type resolution for 10 of them
  • Releases are VirusTotal-scanned and SLSA 3 attested

Weaknesses

  • Updates require re-running the install script; `update` only prints the command
  • Defender may flag release binaries as a false positive, per the README
  • All active processes must share the exact same build and cache root
  • Watcher covers only git projects opened in MCP sessions, by default
  • no GPU
  • Models: nomic-embed-code (bundled, int8, 768d)
  • port 9749

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

More in MCP servers for developers