Skip to main content
Glama
ManiaSacha

gitlog-mcp

by ManiaSacha
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to gitlog-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-git-chronicle

      luckdevx
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides AI coding agents with Git repository history analysis, including churn hotspot detection, semantic file coupling, and recent context summaries through MCP tools.
      MIT

    • devcontract

      maazbin
      A
      license
      A
      quality
      C
      maintenance
      Enables AI coding agents to retrieve cited git-history explanations for files and tickets, compile a Team Engineering Contract from repository artifacts, and follow guided Understand/Build workflows over MCP stdio. It lets clients such as Grok, Claude Code, Codex, Kiro, and Cursor share the same tools for evidence-backed repository understanding.
      1
      10 npm
      Apache 2.0

    • Continuum

      devjoaocastro
      A
      license
      Not graded
      quality
      D
      maintenance
      Automatically extracts architectural decisions, patterns, and insights from Git commits to build a local, structured project memory. It exposes this living context to AI tools via MCP, allowing them to understand the historical reasoning and evolution behind your codebase.
      9 npm
      7
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools have distinct purposes: changelog vs. release_notes share overlap in generating summaries from commit ranges/tags, which could cause confusion. However, the others are clearly separated.

    Naming Consistency4/5

    All tool names use a consistent verb_noun pattern (changelog is a noun but functions as a verb, minor deviation). Names are clear and predictable.

    Tool Count5/5

    6 tools is well-scoped for a Git log/analysis server, covering key operations without bloat.

    Completeness4/5

    Covers commit analysis, search, blame, release notes, and health metrics. A possible gap is direct diff retrieval between commits, but core workflows are well-supported.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources