Skip to main content
Glama

Related Servers

Alternatives to git-graph

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables terminal-based Git graph viewing and commit/range selection, while exposing bounded Git context such as status, diff, history, and search to MCP clients over local stdio with a read-only default workflow.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A local-first MCP server that provides read-only access to Git repository history, exposing commit metadata and optionally content patches via configurable policies, with optional AI-powered analysis while never modifying Git state.
      14 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to read and investigate git history through MCP, including blame, diffs, old file versions, and automated bisect to find when a bug was introduced.
      4 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to inspect local Git repositories through five focused, read-only tools for repository trees, literal text search, numbered file reads, bounded git diffs, and project summaries while confining paths, skipping secret-like and binary files, and enforcing output limits.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Gives MCP clients a read-only, evidence-based view of explicitly approved local projects and individual Codex sessions, enabling codebase browsing, session review, and comparison of session records against current source and bounded Git history without modifying sources or controlling sessions.
      MIT

    TDQS

    B3.4/5.0

    Scored across 2 tools

    Disambiguation4/5

    git_history shows a graph overview of commits and branches, while git_commit retrieves detailed metadata and patch for a specific hash. The two purposes are clearly different, though both operate on commit history and could be slightly confused by an agent skimming descriptions.

    Naming Consistency5/5

    Both tools follow a consistent `git_` prefix with snake_case nouns: `git_history` and `git_commit`. The pattern is predictable and readable, with no mixed conventions.

    Tool Count3/5

    Two tools is thin for a server focused on Git graph exploration, sitting at the borderline identified in the calibration. Additional tools for branch listing, searching, or diffing would make the set feel more complete without being excessive.

    Completeness3/5

    The server covers viewing the commit graph and inspecting a specific commit, but notable read-only operations are missing: branch/tag listing, searching or filtering history, file-level history, and showing diffs between arbitrary commits. These gaps limit deeper Git exploration workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues