Skip to content
MCP server

CommitLore

Git-native decision memory that tells coding agents which past choices still apply

Pricing
Open source
Platforms
CLI, API, vscode
Version
1.2.0
Listing updated
today

Similar MCP servers

About CommitLore

CommitLore is an open-source MCP server for developer tools. It is available on CLI, API, vscode and self-hosted.

CommitLore keeps the reasoning behind a codebase next to the code: constraints, rejected alternatives and warnings that a diff alone does not show. The records are stored as Git trailers or notes rather than in a hosted database, so they branch, merge and clone with the repository they describe.

Before an agent edits a file, CommitLore returns only the decisions that are still active for that path. Superseded and expired records are kept distinct, so an agent is not handed a choice the team already reversed. Each record carries a trust grade, and the README says delivered records are weighed as information rather than enforced as orders by default.

It suits teams using Claude Code, Codex or other MCP-capable agents on repositories with a long history of rejected approaches. The README describes capture as assisted rather than automatic, so a repository with few recorded decisions gets little benefit.

What it does

Git-stored decision records
Accepted records live in Git trailers or notes, with no hosted memory database involved.
Path-scoped delivery
Only decisions active for the file an agent is about to edit are returned.
Lifecycle tracking
Active, superseded and expired decisions are kept distinct so old choices do not resurface as current guidance.
Trust grading
Records are delivered as directives, claims or withheld content, with an optional signed-authority mode.
Pre-edit context delivery
Supported agent hosts receive current context before an edit through a plugin hook or MCP.
Squash-merge preservation
An optional GitHub Action carries records across squash merges made on the GitHub server.

Good for

  • Stop an agent from re-proposing an approach the team already rejected
  • Record non-obvious constraints behind a pricing or business rule for later contributors
  • Preserve warnings about traps hit during a fix so the next session avoids them
  • Check whether a previously retired design choice still applies before changing a module

Pricing

Open source

MIT licensed; no paid hosted plan described.

CommitLore FAQ

Does CommitLore send repository data to a hosted service?

The README says there is no hosted backend and records live in Git. It also notes that once context is returned, the host agent handles it under its own policy.

Does every commit get a record?

No. Most commits should carry no record, and the README says capture is assisted rather than deterministic on every commit.

What agents are supported?

The README lists Claude Code and Codex with plugin integration, and Hermes after a separate install. Gemini CLI, Cursor, Windsurf and opencode receive delivery over MCP where the host supports it.

Is the directive mode a form of authentication?

No. The README states that default directive mode matches the commit author header, which can be set by anyone who can write a commit. Signed mode additionally requires Git verification and a signer allowlist.

Is CommitLore free?

Yes. CommitLore is open source, so you can use and self-host it for free.

What are the best alternatives to CommitLore?

The closest alternatives to CommitLore are RepoMemory, Unl, Limpet, Lockstep AI and Link.

Where this comes from

  • Description: written from the project's README and its MCP Registry entry.

How AIPoweredBot checks servers