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

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

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

Which MCP server has more tools and community activity?

ContextLattice lists 6 tools with 3 views and 153 GitHub stars. Codebase Memory MCP lists 14 tools with 7 views and 42,895 GitHub stars.

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

ContextLattice vs Codebase Memory MCP

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

ContextLattice

Knowledge & Memory · Local stdio

Quality: 49/100 (Fair) | Auth: API Key required

Codebase Memory MCP

Knowledge & Memory · Local stdio

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

Verdict Summary: Choose ContextLattice 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 ContextLattice when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
Primary tools included: Durable mission and project context, Provenance-aware staged retrieval, Signed and bounded context transfer.

Explore ContextLattice 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	ContextLattice sheawinkler Knowledge & Memory	Codebase Memory MCP DeusData Knowledge & Memory
Summary	Private-by-default memory and context layer for agents with Go/Rust runtime, staged retrieval across fused data backends, and long-horizon context continuity.	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

Tools & Capabilities Breakdown

ContextLattice Tools (6)

Durable mission and project context

Provenance-aware staged retrieval

Signed and bounded context transfer

Verified outcome and skill promotion workflow

Local-first storage with opt-in aggregate signals

CLI, HTTP, and MCP integration surfaces

Codebase Memory MCP Tools (14)

index_repository

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

ContextLattice Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "sheawinkler-contextlattice": {
      "command": "npx",
      "args": [
        "-y",
        "sheawinkler-contextlattice"
      ]
    }
  }
}

Codebase Memory MCP Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

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

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