CommitLore vs Adrkit decision memory

In-depth architectural comparison of the CommitLore and Adrkit decision memory 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?

C

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

Choose Adrkit decision memory 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 Adrkit decision memory Details

Feature & Specification Comparison

Specification	C CommitLore Knowledge & Memory	Adrkit decision memory Knowledge & Memory
Summary	Git-native decision memory for coding agents: only the decisions still in force for the edited path	Deterministic, offline, read-only ADR decision memory for coding agents. No model or network calls.
Category & Scope	Knowledge & Memory	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": {
    "commitlore": {
      "command": "npx",
      "args": [
        "-y",
        "commitlore"
      ]
    }
  }
}

{
  "mcpServers": {
    "adrkit-decision-memory": {
      "command": "npx",
      "args": [
        "-y",
        "@adrkit/cli"
      ]
    }
  }
}

Related MCP Server Comparisons