Skip to main content
Glama
MongLong0214

CommitLore

by MongLong0214
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to CommitLore

No user-submitted related servers found.

    Related Servers

    • whynot

      Stakenshake
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to record rejected approaches, decisions, and constraints, with expiring reasons, in a git-tracked Markdown store the agent consults before proposing anything. This makes agents stop re-suggesting options that were already ruled out, and entries quietly drop out of view once they lapse.
      103 npm
      1
      MIT

    • infernoflow

      ronmiz
      A
      license
      B
      quality
      A
      maintenance
      Git-native memory for coding agents, so every session starts warm. Gotchas, decisions, dead ends and bookmarks are saved as plain JSONL in your repo; Claude Code, Cursor and Copilot read them, and teammates get them through git.
      9
      303 npm
      8
      MIT

    • beadless

      KuraPiee
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides AI coding agents with git-native persistent memory and a dependency-aware task graph, letting them record and fuzzy-recall architectural decisions, lessons, and gotchas while creating, claiming, and completing tasks that auto-unblock downstream work. Stores everything as plain JSON and Markdown committed inside the repository, so context stays branch-aware, team-shared, and reviewable in pull requests.
      6 npm
      MIT

    • Projectmem

      riponcm
      A
      license
      A
      quality
      A
      maintenance
      Local-first memory layer for AI coding agents — captures issues, attempts, fixes, and decisions, and warns at git commit before you repeat a mistake.
      17
      810 PyPI
      866
      MIT

    • memini

      lumayapartners
      A
      license
      A
      quality
      D
      maintenance
      Local-first project memory for AI coding agents. Records failed attempts, fragile files, and decisions per repo, and warns the agent via hooks before it repeats a recorded mistake.
      6
      0
      MIT

    • Alethea

      fpavia111-creator
      A
      license
      B
      quality
      B
      maintenance
      Enables coding agents to persist and retrieve ADR-style decisions and machine-checkable constraints as git-friendly markdown in a repository, linked to requirement ids, tests and commits. Agents can pull relevant context before a task, check a proposed change against accepted constraints before committing, and record, supersede or search decisions over a local stdio connection.
      7
      143 npm
      MIT
    Deploy Server
    Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A4/5.0

    Scored across 8 tools

    Disambiguation3/5

    The capture lifecycle tools (prepare/verify/stage) are clearly separated by phase, and stale/runtime_identity are distinct. However, before_change, query, and guard overlap: before_change already runs the guard when a proposal is supplied, and query also returns ruled-out alternatives for a path. The descriptions help, but an agent could easily pick the wrong one for a pre-edit context lookup.

    Naming Consistency4/5

    All tools share the commitlore_ prefix and use lowercase snake_case, which is a clear and consistent pattern. The capture tools use verb_noun (prepare_capture, verify_capture, stage_capture), but before_change, stale, and runtime_identity are stylistic deviations, so the set is mostly consistent rather than fully uniform.

    Tool Count5/5

    Eight tools is well-scoped for this server's purpose: three for the capture pipeline, three for reading/guarding context, plus stale and runtime identity. Each tool has a place and the set feels neither bloated nor thin.

    Completeness4/5

    The core workflow is covered: retrieving records/context, checking proposals, and the prepare/verify/stage capture pipeline. Minor gaps exist—such as no direct way to update, dismiss, or resolve stale records—but these are workable and may be intentionally outside the MCP surface.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources