codebase-memory-mcp and mcp-codebase-index
These are direct competitors—both index codebases for efficient MCP-based search, but A emphasizes persistent knowledge graphs with broader language support while B focuses on structural navigation tools (functions, classes, dependency graphs) with lower barrier to adoption (zero dependencies, higher monthly downloads).
About codebase-memory-mcp
DeusData/codebase-memory-mcp
MCP server that indexes your codebase into a persistent knowledge graph. 64 languages, sub-ms queries, 99% fewer tokens than grep. Single Go binary, no Docker, no API keys.
This tool helps developers understand their codebases more efficiently, especially when working with AI coding agents. It ingests your entire codebase, analyzing its structure across 66 programming languages, and outputs a persistent knowledge graph of functions, classes, and call chains. Developers, particularly those using AI agents for coding tasks, would use this to quickly query and visualize their project's architecture.
About mcp-codebase-index
MikeRecognex/mcp-codebase-index
17 MCP query tools for codebase navigation — functions, classes, imports, dependency graphs, change impact. Zero dependencies. 87% token reduction.
This tool helps software developers quickly understand and navigate large codebases. It takes your source code files (Python, TypeScript, Go, Rust, C#, Markdown) and creates a detailed map of functions, classes, imports, and dependencies. The output is a structured index that AI assistants like Claude Code can use to answer questions about the code, find specific elements, and trace dependencies much faster than reading files directly. It's designed for developers working on complex software projects.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work