codebase-memory-mcp vs MCP Python SDK

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 +333 for MCP Python SDK.
  • Pick codebase-memory-mcp for: mCP server indexing codebases into a persistent knowledge graph with tree-sitter and hybrid LSP. Pick MCP Python SDK for: the official Python SDK for Model Context Protocol servers and clients.

From GitHub data refreshed daily.

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

MCP Python SDKopen-source

The official Python SDK for Model Context Protocol servers and clients

Metrics

codebase-memory-mcpMCP Python SDK
Stars45.6k24.4k
Star velocity /mo1.5k332.5531914893617
Commits (90d)2.1k93
Releases (6m)1010
Overall score0.90542355470122440.7435202335582256

Pros

    • +Official implementation with comprehensive MCP protocol support including resources, tools, prompts, and structured output capabilities
    • +Multiple deployment options from development mode to production ASGI server integration with Claude Desktop compatibility
    • +Advanced features like context management, authentication, elicitation, sampling, and streamable HTTP transport for flexible AI integration

    Cons

      • -Currently in version transition with v2 being pre-alpha and in development, potentially causing breaking changes
      • -Complexity may be overkill for simple AI tool integrations that don't need full MCP protocol compliance

      Use Cases

        • •Building MCP servers to connect AI assistants to databases, APIs, or file systems with standardized security
        • •Creating AI-enabled applications that need structured tool calling and resource access capabilities
        • •Integrating existing ASGI web applications with MCP protocol support for AI assistant connectivity

        FAQ

        Which is more popular, codebase-memory-mcp or MCP Python SDK?
        codebase-memory-mcp has more GitHub stars (45,600 vs 24,449).
        Which is more actively developed, codebase-memory-mcp or MCP Python SDK?
        codebase-memory-mcp had more commits in the last 90 days (2,148 vs 93).
        Should I use codebase-memory-mcp or MCP Python SDK?
        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.