codebase-memory-mcp vs MCP Inspector

Side-by-side comparison of two AI agent tools

Short answer

  • codebase-memory-mcp is growing faster: +1,470 GitHub stars in the last 30 days vs +282 for MCP Inspector.
  • Pick codebase-memory-mcp for: mCP server indexing codebases into a persistent knowledge graph with tree-sitter and hybrid LSP. Pick MCP Inspector for: visual testing tool for MCP servers.

From GitHub data refreshed daily.

c

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

Visual testing tool for MCP servers

Metrics

codebase-memory-mcpMCP Inspector
Stars45.6k11.0k
Star velocity /mo1.5k281.96808510638294
Commits (90d)2.1k1.8k
Releases (6m)1010
Overall score0.90542355470122440.8282768771357465

Pros

    • +提供直观的可视化界面，无需复杂的命令行操作即可测试 MCP 服务器
    • +支持多种传输协议（stdio、SSE、streamable-http），兼容性强
    • +零配置快速启动，通过 npx 命令即可直接运行，开发体验极佳

    Cons

      • -需要 Node.js 22.7.5+ 环境，对运行环境有特定要求
      • -主要面向 MCP 服务器开发者，普通用户使用场景有限
      • -作为调试工具，不适合生产环境部署使用

      Use Cases

        • •MCP 服务器开发过程中的功能验证和调试测试
        • •集成 MCP 服务器到应用前的接口兼容性检查
        • •MCP 协议实现的教学演示和原型验证
        View codebase-memory-mcp DetailsView MCP Inspector Details

        FAQ

        Which is more popular, codebase-memory-mcp or MCP Inspector?
        codebase-memory-mcp has more GitHub stars (45,600 vs 10,997).
        Which is more actively developed, codebase-memory-mcp or MCP Inspector?
        codebase-memory-mcp had more commits in the last 90 days (2,148 vs 1,760).
        Should I use codebase-memory-mcp or MCP Inspector?
        Compare their capabilities, limitations and "best for" notes above. Trying each on a small task is the fastest way to decide.