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

Core 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 Core 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 Core and Codebase Memory MCP free or paid?

Core 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?

Core lists 25 tools with 0 views and 215 GitHub stars. Codebase Memory MCP lists 14 tools with 7 views and 42,594 GitHub stars.

Can I use both Core 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

Core vs Codebase Memory MCP

In-depth architectural comparison of the Core 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

Core

Knowledge & Memory · Local stdio

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

Codebase Memory MCP

Knowledge & Memory · Local stdio

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

Verdict Summary: Choose Core 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 Core 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: omega_store, omega_query, omega_welcome.

Explore Core 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, list_projects, delete_project.

Explore Codebase Memory MCP Details

Feature & Specification Comparison

Specification	C Core Knowledge & Memory	Codebase Memory MCP DeusData Knowledge & Memory
Summary	Persistent memory for AI coding agents. #1 on LongMemEval. 26 MCP tools. Local-first.	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
Category & Scope	Knowledge & Memory

Tools & Capabilities Breakdown

Core Tools (25)

omega_store

Store typed memory (decision, lesson, error, summary)

omega_query

Semantic search with tag filters and contextual re-ranking

omega_welcome

Session briefing with recent memories and profile

omega_profile

Read or update user profile

omega_delete_memory

Delete a specific memory by ID

omega_edit_memory

Edit the content of a memory

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).

Core Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "core-2": {
      "command": "uvx",
      "args": [
        "omega-memory"
      ]
    }
  }
}

Codebase Memory MCP Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

Core 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 Core when you need capabilities focused on knowledge & memory and Codebase Memory MCP when you require tools for knowledge & memory.

More alternatives to Core More alternatives to Codebase Memory MCP Knowledge & Memory category hub