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

Codebase Memory MCP belongs to the Knowledge & Memory category with local stdio execution, while DoneThat belongs to the Knowledge & Memory category with local stdio execution.

How do I install Codebase Memory MCP or DoneThat 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 Codebase Memory MCP and DoneThat free or paid?

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

Which MCP server has more tools and community activity?

Codebase Memory MCP lists 17 tools with 7 views and 43,832 GitHub stars. DoneThat lists 0 tools with 1 views and 0 GitHub stars.

Can I use both Codebase Memory MCP and DoneThat 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

Codebase Memory MCP vs DoneThat

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

Codebase Memory MCP

Knowledge & Memory · Local stdio

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

DoneThat

Knowledge & Memory · Local stdio

Quality: 37/100 (Fair) | Auth: No auth required

Verdict Summary: Choose Codebase Memory MCP if you need specialized Knowledge & Memory tools running via a local process. Choose DoneThat 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 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

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

Feature & Specification Comparison

Specification	Codebase Memory MCP DeusData Knowledge & Memory	D DoneThat 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	Privacy-first work tracking with summaries, reports, coaching, and AI-ready long-term memory.
Category & Scope	Knowledge & Memory

Tools & Capabilities Breakdown

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.

get_code_snippet

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

Codebase Memory MCP Configuration

mcpServers (Claude Desktop / Cursor)

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

DoneThat Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

Codebase Memory MCP is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, DoneThat belongs to Knowledge & Memory using local stdio subprocess. Select Codebase Memory MCP when you need capabilities focused on knowledge & memory and DoneThat when you require tools for knowledge & memory.

More alternatives to Codebase Memory MCP More alternatives to DoneThat Knowledge & Memory category hub