What is the key difference between Kage and Codebase Memory MCP?

Kage belongs to the Knowledge & Memory category with local stdio execution, while Codebase Memory MCP belongs to the Knowledge & Memory category with local stdio execution.

How do I install Kage or Codebase Memory MCP in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Kage and Codebase Memory MCP free or paid?

Kage operates under a Free / Open Source model (No auth required). Codebase Memory MCP operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Kage lists 6 tools with 3 views and 33 GitHub stars. Codebase Memory MCP lists 17 tools with 7 views and 43,562 GitHub stars.

Can I use both Kage and Codebase Memory MCP together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Kage vs Codebase Memory MCP

In-depth architectural comparison of the Kage and Codebase Memory MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Kage

Knowledge & Memory · Local stdio

Quality: 56/100 (Good) | Auth: No auth required

Codebase Memory MCP

Knowledge & Memory · Local stdio

Quality: 73/100 (Great) | Auth: No auth required

Verdict Summary: Choose Kage if you need specialized Knowledge & Memory tools running via a local process. Choose Codebase Memory MCP if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Kage when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: OKF-compatible Markdown memory in Git, Citation validation at write and recall time, Local BM25 and vector retrieval.

Explore Kage Details

Choose Codebase Memory MCP when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: index_repository, search_graph, query_graph.

Explore Codebase Memory MCP Details

Feature & Specification Comparison

Specification	Kage kage-core Knowledge & Memory	Codebase Memory MCP DeusData Knowledge & Memory
Summary	Verified, git-native memory for coding agents. Memory is plain JSON packets committed in your repo, each checked against the code it cites — hallucinated citations rejected at write, stale or changed memory withheld at recall, plus diff-time stale-catch. Local-only (BM25 + vectors), no account, no API key. npx -y @kage-core/kage-graph-mcp install	Code-intelligence engine that indexes a repo into a persistent knowledge graph — functions, classes, call chains, HTTP routes, cross-service links. 159 languages via tree-sitter + Hybrid LSP, sub-ms structural queries, 99% fewer tokens than grep. Single static binary, zero dependencies, 100% local. npx codebase-memory-mcp

Tools & Capabilities Breakdown

Kage Tools (6)

OKF-compatible Markdown memory in Git

Citation validation at write and recall time

Local BM25 and vector retrieval

Isolated worktree orchestration

Independent test, diff, and citation checks

Agent setup and local project UI

Codebase Memory MCP Tools (17)

index_repository

Index a repository. full/moderate add semantics; fast omits them; cross-repo-intelligence links services. Reports coverage gaps.

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Kage Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "kage-core-kage": {
      "command": "npx",
      "args": [
        "-y",
        "@kage-core/kage-graph-mcp"
      ]
    }
  }
}

Codebase Memory MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "deusdata-codebase-memory-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "codebase-memory-mcp"
      ]
    }
  }
}

Frequently Asked Questions

Kage is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Codebase Memory MCP belongs to Knowledge & Memory using local stdio subprocess. Select Kage when you need capabilities focused on knowledge & memory and Codebase Memory MCP when you require tools for knowledge & memory.

More alternatives to Kage More alternatives to Codebase Memory MCP Knowledge & Memory category hub Canonical compare URL