What is the key difference between Mimir — Persistent Memory Engine and Codebase Memory MCP?

Mimir — Persistent Memory Engine belongs to the Knowledge & Memory category with cloud HTTP/SSE execution, while Codebase Memory MCP belongs to the Knowledge & Memory category with local stdio execution.

How do I install Mimir — Persistent Memory Engine 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.

Which MCP server has more tools and community activity?

Mimir — Persistent Memory Engine lists 0 tools with 0 views and 0 GitHub stars. Codebase Memory MCP lists 14 tools with 7 views and 42,236 GitHub stars.

Can I use both Mimir — Persistent Memory Engine 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

Mimir — Persistent Memory Engine vs Codebase Memory MCP

Q: Are Mimir — Persistent Memory Engine and Codebase Memory MCP free or paid?

Mimir — Persistent Memory Engine operates under a Free / Open Source model (No auth required). Codebase Memory MCP operates under a Free / Open Source model (No auth required).

In-depth architectural comparison of the Mimir — Persistent Memory Engine 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

Mimir — Persistent Memory Engine

Knowledge & Memory · Remote HTTP/SSE

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

Codebase Memory MCP

Knowledge & Memory · Local stdio

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

Verdict Summary: Choose Mimir — Persistent Memory Engine if you need specialized Knowledge & Memory tools running via a hosted cloud SSE transport. 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 Mimir — Persistent Memory Engine when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Mimir — Persistent Memory Engine 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	M Mimir — Persistent Memory Engine Knowledge & Memory	Codebase Memory MCP DeusData Knowledge & Memory
Summary	Persistent memory for AI agents. 36+ MCP tools: encryption, decay, hybrid search, knowledge graph.	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

Mimir — Persistent Memory Engine Tools (0)

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

Codebase Memory MCP Tools (14)

index_repository

Index a repository into the graph. Auto-sync keeps it fresh after that.

list_projects

List all indexed projects with node/edge counts.

delete_project

Remove a project and all its graph data.

index_status

Check indexing status of a project.

search_graph

Structured search by label, name pattern, file pattern, degree filters. Pagination via limit/offset.

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

Mimir — Persistent Memory Engine Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "mimir-persistent-memory-engine": {
      "url": "https://perseus.observer"
    }
  }
}

Codebase Memory MCP Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

Mimir — Persistent Memory Engine is categorized under Knowledge & Memory and uses a remote streaming HTTP/SSE transport. In contrast, Codebase Memory MCP belongs to Knowledge & Memory using local stdio subprocess. Select Mimir — Persistent Memory Engine when you need capabilities focused on knowledge & memory and Codebase Memory MCP when you require tools for knowledge & memory.

More alternatives to Mimir — Persistent Memory Engine More alternatives to Codebase Memory MCP Knowledge & Memory category hub Canonical compare URL