bloop vs codebase-memory-mcp

Side-by-side comparison of two AI agent tools

bloopopen-source

bloop is a fast code search engine written in Rust.

High-performance code intelligence MCP server. Indexes codebases into a persistent knowledge graph — average repo in milliseconds. 158 languages, sub-ms queries

Metrics

bloopcodebase-memory-mcp
Stars9.5k45.6k
Star velocity /mo-3.68983957219251353.8k
Commits (90d)02.1k
Releases (6m)010
Overall score0.11163002302159250.912298123773986

Pros

  • +Blazing fast performance with Rust-based architecture and advanced search indexes powered by Tantivy and Qdrant
  • +Privacy-focused approach with on-device embedding for semantic search, keeping code analysis local
  • +Multiple search capabilities including natural language AI queries, regex search, symbol search, and precise code navigation

    Cons

    • -Requires OpenAI API key for AI-powered features, creating dependency on external service
    • -Code navigation and advanced language features limited to 10+ popular programming languages
    • -Desktop application only, lacking web-based or command-line-first workflows for some use cases

      Use Cases

      • •Explaining how complex files or features work in simple language for code documentation and onboarding
      • •Writing new features using existing codebase as context to maintain consistency and reduce development time
      • •Understanding and working with poorly documented open source libraries by querying code behavior

        FAQ

        Which is more popular, bloop or codebase-memory-mcp?
        codebase-memory-mcp has more GitHub stars (45,551 vs 9,491).
        Which is more actively developed, bloop or codebase-memory-mcp?
        codebase-memory-mcp had more commits in the last 90 days (2,093 vs 0).
        Should I use bloop or codebase-memory-mcp?
        Compare their capabilities, limitations and "best for" notes above. Both are open source, so trying each on a small task is the fastest way to decide.