Skip to main content
Glama
seekingalpha

git-log-mcp

by seekingalpha
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to git-log-mcp

No user-submitted related servers found.

    Related Servers

    • Expert Among Us

      portablestew
      A
      license
      Not graded
      quality
      D
      maintenance
      Indexes commit history to create a queryable expert, providing insights into code evolution, developer intent, and hidden patterns beyond static code analysis.
      MIT

    • git-repo-analyzer-mcp

      AntonyWhatsup
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables analysis of local Git repositories via standard git commands, providing insights like line authorship, commit frequency, code churn, and co-changed files.
      -

    • Git Metrics MCP Server

      jonmatum
      A
      license
      B
      quality
      C
      maintenance
      Analyzes git repository metrics to understand team health, development patterns, code quality, and collaboration through natural language queries. Provides insights on commit statistics, bus factor, velocity trends, technical debt, and burnout detection.
      12
      3 npm
      1
      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

    A4.5/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only a single tool, there is no possibility of confusion between tools. The description explicitly distinguishes it from file reads and branch manipulation, making its purpose clear.

    Naming Consistency5/5

    The single tool name `git_log` follows a clean, conventional snake_case pattern that aligns with the server's purpose. Consistency is trivially maintained with one tool.

    Tool Count4/5

    One tool is slightly under the typical 3-15 range, but for a narrowly scoped git-log server, it is reasonable and not excessive. The tool's flexibility helps compensate for the thin count.

    Completeness4/5

    The tool covers the core need of commit history analysis and change attribution, including messages and diffs. Minor gaps exist for operations like blame or range-specific logs, but the description implies the tool can handle broad historical queries.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources