Codebase Memory MCP vs Sticky

In-depth architectural comparison of the Codebase Memory MCP and Sticky 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.

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, search_graph, query_graph.

Explore Codebase Memory MCP Details

S

Choose Sticky 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 Sticky Details

Feature & Specification Comparison

Specification	Codebase Memory MCP DeusData Knowledge & Memory	S Sticky 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	A board your agent writes to. Persistent memory, capped so context never grows.
Category & Scope	Knowledge & Memory

Tools & Capabilities Breakdown

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

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

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

Related MCP Server Comparisons