What is the key difference between MMW Managed Memory Workspace and Codebase Memory MCP?

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

MMW Managed Memory Workspace 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?

MMW Managed Memory Workspace lists 0 tools with 0 views and 0 GitHub stars. Codebase Memory MCP lists 17 tools with 7 views and 44,933 GitHub stars.

Can I use both MMW Managed Memory Workspace 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

MMW Managed Memory Workspace vs Codebase Memory MCP

In-depth architectural comparison of the MMW Managed Memory Workspace 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

MMW Managed Memory Workspace

Knowledge & Memory · Local stdio

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

Codebase Memory MCP

Knowledge & Memory · Local stdio

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

Verdict Summary: Choose MMW Managed Memory Workspace 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 MMW Managed Memory Workspace 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 MMW Managed Memory Workspace 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, search_graph, query_graph.

Explore Codebase Memory MCP Details

Feature & Specification Comparison

Specification	M MMW Managed Memory Workspace Knowledge & Memory	Codebase Memory MCP DeusData Knowledge & Memory
Summary	Ultra-fast persistent memory workspace with tenant isolation and cross-model 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

MMW Managed Memory Workspace Tools (0)

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

Codebase Memory MCP Tools (17)

index_repository

Index a repository. full/moderate add semantics; fast omits them; cross-repo-intelligence links services. Reports coverage gaps.

search_graph

Find symbols via BM25 query, regex name/qn filters, or semantic_query. Rows keep qn/file/lines and in/out over CALLS/USAGE/CALL_REFERENCE/INHERITS/IMPLEMENTS.

query_graph

Read-only Cypher for multi-hop, aggregation, complexity, or cross-service analysis. Default: 200 visible rows with exact/lower-bound totals and truncation; continue safely with next_cursor. graph=missed is a file tree of flagged coverage gaps; absence is not proof of completeness. Use get_graph_schema(diagnostics=full) for properties.

trace_path

Trace callers/callees, data flow, or cross-service paths. Defaults exclude tests and resolver evidence. Rows keep qn/hop with explicit totals, relations, and continuations.

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

MMW Managed Memory Workspace Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "mmw-managed-memory-workspace": {
      "command": "npx",
      "args": [
        "-y",
        "mmw-managed-memory-workspace"
      ]
    }
  }
}

Codebase Memory MCP Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

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

More alternatives to MMW Managed Memory Workspace More alternatives to Codebase Memory MCP Knowledge & Memory category hub Canonical compare URL