codebase-memory-mcp vs ragflow

Side-by-side comparison of two AI agent tools

Short answer

  • Pick codebase-memory-mcp for: mCP server indexing codebases into a persistent knowledge graph with tree-sitter and hybrid LSP. Pick ragflow for: open-source RAG engine combining knowledge retrieval and agent capabilities for LLMs.

From GitHub data refreshed daily.

MCP server indexing codebases into a persistent knowledge graph with tree-sitter and hybrid LSP

ragflowopen-source

Open-source RAG engine combining knowledge retrieval and agent capabilities for LLMs

Metrics

codebase-memory-mcpragflow
Stars45.7k91.6k
Star velocity /mo1.7k2.4k
Commits (90d)2.1k2.7k
Releases (6m)1010
Overall score0.9063711496901890.9150811116917444

Pros

    • +结合了先进的RAG技术和Agent能力,提供比传统RAG更强大的功能
    • +开源且拥有活跃社区支持,GitHub星数超过7.6万,可信度高
    • +提供云服务和Docker容器化部署,支持多种部署方式

    Cons

      • -作为相对复杂的RAG系统,可能需要一定的技术背景才能充分配置和优化
      • -大规模部署可能需要相当的计算资源和存储空间

      Use Cases

        • •企业知识库问答系统,基于内部文档为员工提供智能查询服务
        • •智能客服系统,结合产品文档和FAQ提供准确的客户支持
        • •研究助手应用,帮助研究人员从大量学术文献中检索相关信息

        FAQ

        Which is more popular, codebase-memory-mcp or ragflow?
        ragflow has more GitHub stars (91,600 vs 45,666).
        Which is more actively developed, codebase-memory-mcp or ragflow?
        ragflow had more commits in the last 90 days (2,665 vs 2,093).
        Should I use codebase-memory-mcp or ragflow?
        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.