What is the key difference between Codebase Memory Mcp and VaultCrux Memory Core?

Codebase Memory Mcp belongs to the Knowledge & Memory category with local stdio execution, while VaultCrux Memory Core belongs to the Knowledge & Memory category with local stdio execution.

How do I install Codebase Memory Mcp or VaultCrux Memory Core 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 Codebase Memory Mcp and VaultCrux Memory Core free or paid?

Codebase Memory Mcp operates under a Free / Open Source model (No auth required). VaultCrux Memory Core operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Codebase Memory Mcp lists 14 tools with 6 views and 38,513 GitHub stars. VaultCrux Memory Core lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Codebase Memory Mcp and VaultCrux Memory Core 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.

How do I install Codebase Memory Mcp or VaultCrux Memory Core in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are Codebase Memory Mcp and VaultCrux Memory Core free to use, or do they require API keys?

Codebase Memory Mcp is listed under a Free / Open Source model with No auth required . VaultCrux Memory Core operates under a Free / Open Source model with No auth required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both Codebase Memory Mcp and VaultCrux Memory Core at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both deusdata-codebase-memory-mcp and vaultcrux-memory-core as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Codebase Memory Mcp has a Quality Score of 73 /100 ( Great ) with 6 views, 1 installs, and 38,513 GitHub stars. VaultCrux Memory Core holds a Quality Score of 20 /100 ( Emerging ) with 0 views, 0 installs, and 0 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Codebase Memory Mcp vs VaultCrux Memory Core

In-depth architectural comparison of the Codebase Memory Mcp and VaultCrux Memory Core 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

Codebase Memory Mcp

Knowledge & Memory · Local stdio

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

VaultCrux Memory Core

Knowledge & Memory · Local stdio

Quality: 20/100 (Emerging) | Auth: No auth required

Verdict Summary: Choose Codebase Memory Mcp if you need specialized Knowledge & Memory tools running via a local process. Choose VaultCrux Memory Core 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 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

Choose VaultCrux Memory 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).

Explore VaultCrux Memory Core Details

Feature & Specification Comparison

Specification	Codebase Memory Mcp DeusData Knowledge & Memory	V VaultCrux Memory Core Knowledge & Memory
Summary	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	Remote MCP for VaultCrux Memory Core queries, snapshots, freshness, audits, and contradictions.
Category & Scope	Knowledge & Memory

Tools & Capabilities Breakdown

Codebase Memory Mcp Tools (14)

index_repository

Index a repository into the graph. Auto-sync keeps it fresh after that.

list_projects

List all indexed projects with node/edge counts.

delete_project

Remove a project and all its graph data.

index_status

Check indexing status of a project.

search_graph

Structured search by label, name pattern, file pattern, degree filters. Pagination via limit/offset.

trace_path

BFS traversal — who calls a function and what it calls (alias: `trace_call_path`). Depth 1-5.

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

Codebase Memory Mcp Configuration

mcpServers (Claude Desktop / Cursor)

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

VaultCrux Memory Core Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "vaultcrux-memory-core": {
      "command": "npx",
      "args": [
        "-y",
        "vaultcrux-memory-core"
      ]
    }
  }
}

Frequently Asked Questions

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

More alternatives to Codebase Memory Mcp More alternatives to VaultCrux Memory Core Knowledge & Memory category hub