Version control · MCP server
CommitLore: MCP server, setup and security
CommitLore is an open-source MCP server published on GitHub that lets an AI agent retrieve active decisions and constraints for a path before editing. Its repository has 18 stars and its last commit is from October 18, 2026 and it is licensed under MIT.
What CommitLore does
According to its repository: “Returns active decision records for a path before an agent edits it: constraints, ruled-out alternatives and warnings, stored as git trailers and notes.”
The Model Context Protocol (MCP) is a standard plug between an AI agent and an outside service: once the server is connected, its tools show up in the agent, which decides when to call them. CommitLore is listed under Version control, a category of 17 servers in the directory, where it ranks #10 by stars.
Topics declared by the repository: claude-code, git, agent-memory, ai-memory, codex, coding-agents.
Installing and connecting CommitLore
No package or remote server is declared in the official MCP registry: you install it from source, following the repository README.
It works with any MCP-compatible client (Claude Desktop, Claude Code, Cursor, VS Code, Codex and most recent agents). You add one entry to the client's MCP configuration: server name, start command or URL, environment variables. Project language: TypeScript. Listed systems: macOS, Windows, Linux.
Security: what to check
Connecting an MCP server means installing software that talks straight to your agent: it runs with your rights and the model trusts its tool descriptions. The risk therefore depends on what it can touch and how far its code can be trusted.
None of the risk signals we track (system access, secrets, missing licence, abandonment) applies to CommitLore. That does not replace reading the code.
Good practice: grant only the rights needed (least privilege), require human approval for irreversible actions, and run the AI agent security check.
Project activity and maintenance
Created on July 26, 2026, the MongLong0214/commitlore repository has 18 stars and 3 forks, with 0 open issues. It has more stars than 36% of the servers in the directory. It received changes this month. Version published in the registry: 1.2.0 (August 21, 2026).
Stars measure attention, not quality: a recent, heavily promoted project can collect them fast, while a useful but niche server will have few.
Verdict
CommitLore is a reasonable choice; check the points below before connecting it.
Strengths
- Active project: recent commit
- Listed in the official MCP registry
- Permissive licence (MIT)
Limitations
- Install from source
Alternatives
- GitHub33.9K ★
- GitWarren18 ★
- MCP server azure devops397 ★
- GitLab MCP Server (jmrplens)45 ★
- Atlassian dc MCP105 ★
- Gitlab mr MCP94 ★
Learn more
Frequently asked questions
How do I install CommitLore?
No package is declared in the MCP registry: clone the MongLong0214/commitlore repository, follow its README, then declare the start command in your client's MCP configuration.
Is CommitLore free?
The code is published under the MIT licence and can be used free of charge.
Is CommitLore safe?
No risk signal found (system access, secrets, licence, abandonment). As with any MCP server, keep rights minimal and read the code before sensitive use.
Is it an official server?
Nothing says so: it is a project published by MongLong0214 on GitHub. Check who maintains it before giving it access.
What are the alternatives to CommitLore?
In the same category: GitHub, GitWarren, MCP server azure devops, and GitLab MCP Server (jmrplens). GitHub scores higher on our grid.
Related articles
- Build your own MCP server in 30 minutesOctober 24, 2026
- Automate your inbox with an AI agentOctober 18, 2026
- MCP, A2A, and tool calling: agent protocols explainedOctober 17, 2026
- Build an AI agent with n8n, without codingOctober 16, 2026
Neutrality. No affiliate links. No vendor pays to be reviewed, rated or ranked. Reviews are directed by François Chollet, neutral and factual, and every data point is dated and sourced. How we score