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

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

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

Memex lists 12 tools with 1 views and 12 GitHub stars. Codebase Memory MCP lists 14 tools with 7 views and 42,895 GitHub stars.

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

Memex vs Codebase Memory MCP

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

Memex

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 Memex 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 Memex 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: get_project_context, get_symbol_context, get_recent_decisions.

Explore Memex 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	Memex STiFLeR7 Knowledge & Memory	Codebase Memory MCP DeusData Knowledge & Memory
Summary	Developer context continuity system. Watches your git repos and builds a temporal knowledge graph of modules, symbols, decisions, and open problems via Graphiti + Neo4j, then serves it to any AI coding agent over MCP. Every edge carries a validity window and a confidence score that decays over time. 12 tools across read and write. Install via npx -y stifler-memex-mcp. MIT licensed.	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

Tools & Capabilities Breakdown

Memex Tools (12)

get_project_context

Session start. Returns a cluster-level briefing under 1500 tokens regardless of repo size

get_symbol_context

Before editing a function or class. Returns callers, callees, linked decisions

get_recent_decisions

Last N days of architectural decisions, optionally module-scoped

get_open_problems

Active bugs and tech debt, sorted by severity

search_context

Hybrid search: semantic × keyword × graph traversal × RRF merge

get_stale_context

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

Memex Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "stifler7-memex": {
      "command": "npx",
      "args": [
        "-y",
        "stifler-memex-mcp"
      ]
    }
  }
}

Codebase Memory MCP Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

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

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