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

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

VaultCrux Memory 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?

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

Can I use both VaultCrux Memory 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.

How do I install VaultCrux Memory Core or Codebase Memory Mcp 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 VaultCrux Memory Core and Codebase Memory Mcp free to use, or do they require API keys?

VaultCrux Memory Core is listed under a Free / Open Source model with No auth required . Codebase Memory Mcp 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 VaultCrux Memory Core and Codebase Memory Mcp at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both vaultcrux-memory-core and deusdata-codebase-memory-mcp 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, VaultCrux Memory Core has a Quality Score of 20 /100 ( Emerging ) with 0 views, 0 installs, and 0 GitHub stars. Codebase Memory Mcp holds a Quality Score of 73 /100 ( Great ) with 6 views, 1 installs, and 38,510 GitHub stars.

Side-by-Side Model Context Protocol Comparison

VaultCrux Memory Core vs Codebase Memory Mcp

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

VaultCrux Memory Core

Knowledge & Memory · Local stdio

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

Codebase Memory Mcp

Knowledge & Memory · Local stdio

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

Verdict Summary: Choose VaultCrux Memory 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 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

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

VaultCrux Memory Core Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

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.

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

VaultCrux Memory Core Configuration

mcpServers (Claude Desktop / Cursor)

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

Codebase Memory Mcp Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

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

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